rogeriochaves / npm-force-resolutions

Force npm to install a specific transitive dependency version

rogeriochaves/npm-force-resolutions Issues

ENOENT: no such file or directory, open './package-lock.json'
Updated a month ago20
Npm i doesn't fix the dependencies while npm install does
Updated 8 months ago2
Custom registry is sensitive to trailing "/"
Closed a year ago2
npm preinstall fails but not when I run npx npm-force-resolutions
Closed 3 years ago2
Support for multiple versions of same package
Updated a year ago7
Question: If I add a resolution for a dependency, will it get version updates
Updated a year ago1
Does the `overrides` functionality of npm v8 make this tool obsolete?
Updated 2 years ago3
cant install webpack 5 in angular
Closed 2 years ago3
Crash if package-lock contains merge conflict
Updated 2 years ago2
Running the tool reorders `dependencies` within my package-lock.json
Updated 2 years ago4
Order of "dependencies" object keys is being randomized
Updated 2 years ago4
Tool does not work in NPM workspaces
Updated 2 years ago
Can we configure timeout for force-resolutions or increase it?
Updated 2 years ago8
Shouldn't the directions be to run this during "prepublish", not "preinstall"?
Updated 2 years ago1
Broken with NPM >= 8.6.0
Closed 2 years ago2
Invalid Version: >=5.1.1
Updated 2 years ago5
How to specify an http proxy?
Updated 2 years ago6
Difference to npm's overrides unclear
Updated 2 years ago2
Error require() of ES Module not supported.
Updated 2 years ago1
Are wildcards supported?
Updated 2 years ago
Timeout fetching resolutions after upgrading from 0.0.5 to 0.0.10
Updated 3 years ago
Fails in CircleCI
Closed 3 years ago2
Cannot update the package in requires
Updated 3 years ago1
Missing LICENSE file
Updated 3 years ago
Don't modify `package-lock.json` during `npm ci`
Updated 3 years ago3
`npm ci` fails unexpectedly in some projects after resolutions applied
Updated 3 years ago
Package resolution become extraneous.
Updated 3 years ago5
feature: remove transitive dependency
Updated 3 years ago2
RFC: Add a newline to the end of the generated package-lock.json
Updated 3 years ago1
This is only useful for top-level packages
Updated 3 years ago4
npx npm-force-resolutions in preinstall Doesn't Work without Doing npm i npm-force-resolutions First
Closed 3 years ago1
npm audit false negative after npm-force-resolutions
Updated 3 years ago
Npm install fails in npm-force-resolutions if there is a space in the user folder
Updated 3 years ago5
Error: ENOENT: no such file or directory, open './package-lock.json'
Updated 3 years ago3
npm ERR! code ELIFECYCLE
Updated 3 years ago1
Applying resolutions does not work for all dependencies with npm version 7
Closed 3 years ago4
Does not work for generic-names sub-dependency of babel-plugin-react-css-modules
Updated 3 years ago
Indentation being changed in the package-lock
Updated 3 years ago3
not working anymore
Closed 3 years ago19
re-find must match against a string
Closed 3 years ago2
.npmrc private registries ignored since 0.0.3
Closed 3 years ago7
npm-force-resolutions fails, breaking npm i
Closed 3 years ago7
version 0.0.4 cannot find module error
Closed 3 years ago18
0.0.4 breaks builds. Can't find _npx folder.
Closed 3 years ago1
Incorrectly removing "requires" from package lock
Closed 3 years ago2
Question: Apply only on specific base dependencies
Updated 4 years ago
Global Packages?
Updated 4 years ago
Bail out gracefully when running inside Yarn?
Updated 4 years ago1
Fails on Windows 10 because a directory is not being quoted
Updated 4 years ago2
fails when there is a space in the path
Closed 5 years ago1