-
Notifications
You must be signed in to change notification settings - Fork 28
Issues: rogeriochaves/npm-force-resolutions
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Does the
overrides
functionality of npm v8 make this tool obsolete?
#70
opened Sep 21, 2022 by
jayqui
Shouldn't the directions be to run this during "prepublish", not "preinstall"?
#63
opened Jun 20, 2022 by
greim
Timeout fetching resolutions after upgrading from 0.0.5 to 0.0.10
#49
opened Jan 7, 2022 by
bwhite94
npm ci
fails unexpectedly in some projects after resolutions applied
#43
opened Oct 8, 2021 by
wjaspers
Error: ENOENT: no such file or directory, open './package-lock.json'
#36
opened May 10, 2021 by
fredericrous
Does not work for generic-names sub-dependency of babel-plugin-react-css-modules
#35
opened Apr 21, 2021 by
meglio
Can we configure timeout for force-resolutions or increase it?
#33
opened Apr 20, 2021 by
bilalbaqar
Question: If I add a resolution for a dependency, will it get version updates
#31
opened Mar 30, 2021 by
Pranav016
Previous Next
ProTip!
Add no:assignee to see everything that’s not assigned.