Closed hajnyon closed 1 year ago
Hi, I'm a little confused as few notifications were delivered to my email, but there are no responses here. So I guess you removed the answers?
However, I've resolved my issue differently (by fixing all issues that blocked updating the package version). Moreover, on the second look, altering of package-lock.json
doesn't seem as good and more as a "hacky" solution. Feel free to close this issue if you are not going to look in to it more.
A new version is been released recently check the readme to join the discord server if issues are still happening Here is the new version: https://www.npmjs.com/package/force-resolutions?activeTab=readme
Hi, thanks for the effort to provide alternative to npm-force-resolution! I tried to use this package but came across some difficulties. It seems to me it doesn't resolve all versions correctly. I managed to filter this to a minimal setup described below. I am not able to tell if this is a problem with this package or package I'm trying to lock version to.
Steps to reproduce
package.json
After this, package-lock.json has only few versions updated and
npm ls aurelia-loader-webpack
outputs2.2.4
as well:packages.node_modules/aurelia-loader-webpack.version
=2.2.4
- wrongpackages.node_modules/aurelia-webpack-plugin.dependencies.aurelia-loader-webpack
=2.1.0
- correctdependencies.aurelia-loader-webpack.version
=2.2.4
- wrongI hope I described it sufficiently. I can add repository with this example if needed.