-
Notifications
You must be signed in to change notification settings - Fork 386
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Updating my app.js & app.css on theme watch/deploy supposedly fails, but reflects success on the actual storefront #857
Comments
Same issue here. Development build script was more than 4mb and request keep failing. On production build, ~400kb, it was okay. Seems like uploading operation is timing out on large files. To downgrade: |
Same issue, only fails even on attempting to run |
Hi everyone, I am looking into this. @kellyvaughn is the theme that you are running In the most recent release, I added a bunch of timeout settings to try to make hanging requests fail fast however it might have caused requests for large assets to fail now. I will have a test release for you to try in a moment. |
Same issue here, @tanema It's only 40kb - sections/header.liquid |
Hello everyone, please try updating to my fix for this issue |
@tanema This version works for me! |
@tanema It is working now! Thanks for your quick fix. |
Thanks for confirming, I will push out 1.1.4 soon as it has a couple quick fixes from 1.1.3 😬 |
Mate, you're a legend 😎 |
Describe the bug
I am using Laravel Mix to compile all my JavaScript/CSS into one file each.
I run theme watch to detect the newest changes in my compiled JavaScript/CSS (deploy to manually push changes). However, since updating to 1.1.3 this morning, the log keeps reporting failure of the app.js & app.css specifically, even though I am successfully seeing the changes in the browser.
Liquid files still show successful update as expected.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
ThemeKit to report a successful update upon theme watch/deploy.
eg.
Environment:
The text was updated successfully, but these errors were encountered: