-
Notifications
You must be signed in to change notification settings - Fork 270
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
Deploying a webpacker project without sprockets fails #235
Comments
I can think of two solutions:
I kind of like the second option because we can support the next generation of Rails apps using a clean slate rather than hacking the existing tasks with more and more conditional logic. But, the second option is definitely more work. I do not use Capistrano with webpacker so I would need help from the community to put a PR together. Option 1 is fairly easy and I could hack something together for that pretty quickly. Thoughts? |
+1 for the 2nd approach from my side as well, looks cleaner and more future proof :) |
OK I put a |
Does setting the asset_prefix like recommended below work? It worked for me. http://blog.tap349.com/webpack/2018/05/22/webpack-troubleshooting/ edit: I actually had to enable sprockets because of various issues without it :( |
This pull request is necessary when using webpacker and |
Rollback is getting failed when i use |
Steps to reproduce
Deploy a project with assets built with Webpacker and without sprockets generating anything.
Expected behavior
Deploy succeeds
Actual behavior
Deploy fails because manifest files are missing
Hot-Fix
Adding a line to deploy.rb
Rake::Task["deploy:assets:backup_manifest"].clear_actions
The text was updated successfully, but these errors were encountered: