Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What did you implement:
We have a monorepo with several serverless packages. Given the way we do CI and the way
lerna
deals with lockfiles, we actually don't need and don't have an up to dateyarn.lock
, but for our usecase it doesn't really matter.This adds the option
noFrozenLockfile
topackagerOptions
, allowing to runyarn install
without the--no-frozen-lockfile
option. This is as suggested in this comment #369 (comment)I also fixed the documentation for
ignoreScripts
in the README, which mentioned a default value oftrue
when it is in factfalse
How did you implement it:
Added the option in the
install
function inyarn.js
How can we verify it:
I added tests to make sure the option was omitted when using
noFrozenLockfile
Todos:
Is this ready for review?: YES
Is it a breaking change?: NO