-
Notifications
You must be signed in to change notification settings - Fork 763
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
superagent issue #752
Comments
Same problem here, I think it fails because the Node Version is not "13". That shouldn't be the case should it? Otherwise the current "supertest" module will only work where Node 13 is installed. |
You can work around it by using:
|
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. |
Anyways this should be a bug for superagent not for supertest, right? |
It already is, so i think you can close this one: ladjs/superagent#1665 |
Absolutely, what is happening here is just a consequence of the loose dependency to superagent : |
Fixed v6.2.1 released https://github.com/visionmedia/supertest/releases/tag/v6.2.1 |
SuperAgent 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:
The text was updated successfully, but these errors were encountered: