Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Set npm/yarn/pnpm version
See original GitHub issueDescription: Similar to how we can set the node version I’d like to set the npm version.
node-version: 1.16.x
npm-version: 8.5.5
There is a similar issue here https://github.com/actions/setup-node/issues/213, but it’s for a different reason and this one can be resolved by setting the node version. However this is not enough for the problems I have been facing.
Justification: Currently I am struggling with a bug in npm from versions 8.11 to 8.13. These are automatically installed when you chose node version 1.16. This means I have to set back my npm version so the ci can run, which I can do in an extra ci step.
However to me the issue is that the npm version will change over time, without our input. We’d like control over this to prevent issues like the one above from showing up.
Are you willing to submit a PR? Not currently but I might in the future.
Issue Analytics
- State:
- Created a year ago
- Reactions:20
- Comments:6 (1 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Two options for specifying a solution could be querying the
voltasection of the package.json if you manage versions via that, or via theenginesportion of the package.json https://docs.npmjs.com/cli/v8/configuring-npm/package-json#enginesI will be opening a PR on this!