superagent issue
See original GitHub issueSuperAgent Version: 16.2.0 Node Version 16.3 and 12.22.7 OS: Windows
Hello,
I am not quite sure if it is a right spot to post this question. It is an issue with superagent but I don’t personally use superagent. I believe it is installed as part of supertest.
As part of the pipeline to publish package to npm, I run this command to test npm
npm install --no-package-lock --no-production --engine-strict
In the latest 6.2.0 supertest, when I run this command, it is giving me following error, I try the same command in {“npm”:“8.1.0”,“node”:“16.3.0”} as well, no luck. I have to downgrade supertest to 6.1.0 to make it to work:
npm ERR! code ENOTSUP
npm ERR! notsup Unsupported engine for superagent@7.0.1: wanted: {"node":">=6.4.0 !13"} (current: {"node":"12.22.7","npm":"6.14.15"})
npm ERR! notsup Not compatible with your version of node/npm: superagent@7.0.1
npm ERR! notsup Not compatible with your version of node/npm: superagent@7.0.1
npm ERR! notsup Required: {"node":">=6.4.0 !13"}
npm ERR! notsup Actual: {"npm":"6.14.15","node":"12.22.7"}
Issue Analytics
- State:
- Created 2 years ago
- Reactions:2
- Comments:7
Top Results From Across the Web
Issues · ladjs/superagent - GitHub
Ajax for Node.js and browsers (JS HTTP client). Maintained for @forwardemail, @ladjs, @spamscanner, @breejs, @cabinjs, and @lassjs. - Issues ...
Read more >superagent - npm
Small progressive client-side HTTP request library, and Node.js module with the same API, supporting many high-level HTTP client features.
Read more >New Relic SuperAgent (Node)
This code is developed in the open with input from the community through issues and PRs. A New Relic engineering team serves as...
Read more >The Making of a Contact Center Superagent
The superagent is an empowered, knowledgeable and highly skilled ... Problem-solving is considered a fundamental job skill for any customer service rep.
Read more >Full Text Bug Listing - Red Hat Bugzilla
Summary: nodejs-superagent: Information Exposure due to sending the contents of authorization to third parties. Product: [Other] Security Response ...
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
>=6.4.0 !13
I’m not aware of such a syntax for defining semantic versions, the exclamation mark is suitable for architectures and operating systems restrictions, but I haven’t come across anything in that sense for version definitions. If we want to exclude node 13, the syntax should instead be
6.4.0 - 12 || >= 14
Fixed v6.2.1 released
https://github.com/visionmedia/supertest/releases/tag/v6.2.1