[Webpack] Raise an error when lockfile diff is generated #32243
Conversation
|
Thanks for the pull request, and welcome! The Rails team is excited to review your changes, and you should hear from @kaspth (or someone else) soon. If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes. This repository is being automatically checked for code quality issues using Code Climate. You can see results for this analysis in the PR status below. Newly introduced issues should be fixed before a Pull Request is considered ready to review. Please see the contribution instructions for more information. |
| @@ -3,7 +3,7 @@ | |||
| namespace :yarn do | |||
| desc "Install all JavaScript dependencies as specified via Yarn" | |||
| task :install do | |||
| system("./bin/yarn install --no-progress --production") | |||
| system("./bin/yarn install --no-progress --freeze-lockfile --production") | |||
There was a problem hiding this comment.
The option is —frozen-lockfile, not —freeze-lockfile.
https://yarnpkg.com/en/docs/cli/install#toc-yarn-install-frozen-lockfile
Summary
I can't imagine a situation in which you'd want to allow a production yarn install to generate a diff in the lockfile. Inevitably someone will have a problem with this, so I imagine it would go behind a flag, but for everyone else, I think this should be the default