deps: update config to pin dep version for new deps additions #1978
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.
This is just a suggestion that when new packages are added to the repo they are pinned to specific version rather than using the caret (^) and allowing to install different minor versions.
My reasons are:
yarn.lock
when people install deps. Since minor versions are allowedyarn.lock
changes unless contributors install deps with--fozen-lockfile
flag (yarn install --frozen-lockfile
)This just changes the behavior for new packages added.
package.json
would still need to be updated to remove the caret from all deps that have it, but first I wanted to introduce the idea of pinned versions before proceeding to updatepacakge.json