-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
New webpacker:clean task raises 'No such file or directory' error #2372
Comments
Also have the same issue. I did a bit of debug and it's basically occurring because of gz compressed assets. The code in this method https://github.com/LuanGB/webpacker/blob/0c7a9f750ddf3a4fd9a6ad9f91331c80b15c20fd/lib/webpacker/commands.rb#L8 matches finds the original and compressed js file However the ext only pickups up .js As such it tries to delete the js file twice rather than delete the .js and delete .js.gz |
I'm encountering this consistently on our CI and Heroku, the only solution is to clear the whole cache. Issue can recreated easily:
EDIT: recreate instructions |
This solution worked for us, will be great if you can test this patch #2382 |
@tachyons your patch worked great for me.
I was still running into this error due to missing files, so created a follow up PR that ignores missing file errors: #2384 |
@aleksejleonov Sorry, You mean you are still getting missing file error after applying my patch ? |
#2385 - possible solution |
Hi,
you guys added recently a new task
webpacker:clean
which doesn't work for us. Unfortunately we can't prevent this task either because you add it toassets:clean
without giving an option to disable it. Would be great if you could add this.The error is:
We can see in
public/packs
that these files exist beforebut then something in
webpacker:clean
removesand then also complains that thay don't exist anymore.
The text was updated successfully, but these errors were encountered: