-
-
Notifications
You must be signed in to change notification settings - Fork 631
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
Default Production Tasks is not Stopping When Webpack returns non-zero! #733
Comments
Commented on PR, should we just do both? |
100% we need to check the return status... I'm not sure on the |
I think we default to bail early and then they can change it if they want CI to keep running |
This issue is fixed by Webpack V2. Once that is merged...then it's up to the users to configure their package.json appropriately. |
See #730 for a demonstration of how V2 fixes the issue. |
I'll close this issue once I merge the Webpack v2 changes. |
React on Rails is updated for Webpack v2! If you're on webpack v1, use the |
See discussion in #730
https://github.com/shakacode/react_on_rails/blob/master/lib/tasks/assets.rake#L55
@robwise @alexfedoseev I think the bug is that we're not forcing the rake task to fail on the line that's running:
ReactOnRails.configuration.npm_build_production_command
.By contrast, I think we're doing the correct thing here:
https://github.com/shakacode/react_on_rails/blob/master/lib/react_on_rails/test_helper/webpack_assets_compiler.rb#L11
@ypresto Given all this, would it make more sense to just change the code around assets.rake rather than recommending
--bail
?@robwise @alexfedoseev any opnions?
The text was updated successfully, but these errors were encountered: