pin polyfill dependencies in package.json
files
#44
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 doesn't change any of the actual versions of polyfill packages.
Pinning the versions also isn't new, we have lock files.
It only changes how the version was described in
package.json
files.This is intended to make it easier to update other packages with commands like
npm update
.Running
npm update
will no longer affect polyfill package versions.This adds a little bit of hardening against malicious changes in polyfills upstream.
Updating polyfill versions is still fine but should always be done separately from updating other dependencies.