-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Allow Opting Out of Immutable Flags for Yarn 2 #834
Labels
Comments
I'm wondering if it makes sense to allow disabling this via an environment variable. Something that is off by default, but could be set to allow lockfile discrepencies, i.e. |
Any updates here? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In some cases, a user may not want the
--immutable-cache
or--immutable
flag to be passed. One example I have is when you have a repo with some workspace packages that you're not passing to Heroku by adding them to your.slugignore
. In this case, the lock files would change, which means callinginstall --immutable
will fail.Additionally, when
yarn install --immutable
does fail for this reason, there's no indication, and the build just appears to hang.The text was updated successfully, but these errors were encountered: