![]() ![]() The changes can be as specific as we want and scoped, or we can make them generic. I have npm version 5.5.1 and node version v8.9.1. npm update failed to update package.json but a targeted install worked. We can now specify an overrides property in our package.json that enforces the dependency version that is specified there. aliases: up, upgrade Description This command will update all the packages listed to the latest version (specified by the tag config), respecting the semver constraints of both your package and its dependencies (if they also require the same package). npm update Check package.json Environment: OS: Mac OS Big Sur Node: 14.15.5 NPM: 7.5.4 saltire added Bug Needs Triage Release 7.x labels mjlehrke commented on I experienced this bug on Windows, NPM version 6.14.11. ![]() ![]() This was a tedious solution and one that required a lot of maintenance. The most common solution that developers used was to fork Package A, update Package B, and use their fork and maintain it. Install the package using npm -g install tiaanduplessis/pkg-rename Rename your npm module in the package. |_ Package Package B Package B was updated to 2.0.0 and we wanted to use that version (there can be multiple reasons for this, the most common being other packages use the updated one), there was no easy solution for this. ![]()
0 Comments
Leave a Reply. |