fix(TypeScript): npm peer dependency install conflicts in user applications #2699
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.
As pointed out in npm/cli#7719, npm struggles with resolving peer dependencies when running
npm install
and applying new peer dependency requirements that do not align with previously installed versions. In many cases it produces an unexpected error for the user instead of updating installed peer dependency packages.As a (temporary?) workaround, let us avoid using strict peer dependency requirements for our packages.
This changes the
package.json
to use regular dependency version spec even though the expectation is that the install is “flat”, i. e., the packages are is installed on the top-level ofnode_modules/
in the user application.