Update ts-invariant to avoid CSP-violating Function fallback. #7414
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.
Includes this
ts-invariant
PR: apollographql/invariant-packages#53This update may also help with issues like #7406, where a patch version update (from 0.5.0 to 0.5.1) is apparently not enough to force a dependency like
ts-invariant
with multiple conflicting version constraints (from@apollo/client
andgraphql-tools
) to be updated, since version 0.5.0 is still semantically compatible with the desired minimum version 0.5.1, sots-invariant
remains outdated after updating@apollo/client
, despite the new version being clearly mandated in@apollo/client/package.json
.After updating the minor version of
ts-invariant
in package.json (to ^0.6.0), there should be no risk of@apollo/client
incorrectly resolving the olderts-invariant@0.5.0
version, though there may end up being multiple copies ofts-invariant
innode_modules
with different versions, which is fine for this particular package.