Support requiring specific versions of an npm package
See original GitHub issueCurrenty, I can require()
an npm package within a code step, but I cannot specify the version of the package I’d like to use. I’d like support for this.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:19
- Comments:7 (3 by maintainers)
Top Results From Across the Web
How can I specify the required Node.js version in package.json?
You can set the engines field in your package.json and set requirements for either node or npm versions or both: "engines" : {...
Read more >About semantic versioning - npm Docs
Using semantic versioning to specify update types your package can accept. You can specify which update types your package can accept from dependencies...
Read more >NPM: Install Specific Version of a Package - Stack Abuse
This way you can specify a compatible package version, but still get the latest.
Read more >Using npm To Install A Specific Version Of A Node.js Package
Use npm list [package-name] to know the specific latest version of an installed package. Use npm install [package-name]@[version-number] to ...
Read more >How to Install Specific Version of Node.js Package
You can use the below command to install a specific NPM package version. You can mention the required version number after the package...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hi team,
Unfortunately, this issue is the dealbreaker with Pipedream for us also. We can not rely on workflows that can stop working any day.
This is really an important issue. If I we have many workflows running for our clients, we cannot afford having npm package updates breaking our code. The change to a newer version has to be tested properly. At the moment it comes as a possibly negative surprise.
I hope you can soon add this basic functionality of node via something like a package.json.