Temporary fix for npm-force-resolutions #1259
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
See: rogeriochaves/npm-force-resolutions#33 This may not be the proper fix, but I wasn't able to work around the issue and this fixed it. NodeJS v14.21.3 (also tried v18 LTS) NPM v6.14.18
|
Thanks for your contribution @tvdijen I ran into this issue on my maintenance PR where I'm installing NPM updates. The team and us decided to swap NPM for yarn. Yarn is much more robust when it comes to installing resolutions (imho). Combine that with the fact that our other (Stepup) components all use Yarn, the choice was not that hard to make. But this means that I'm closing the PR |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
See: rogeriochaves/npm-force-resolutions#33
This may not be the proper fix, but I wasn't able to work around the issue and this actually fixed it.
NodeJS v14.21.3
NPM v6.14.18