-
Notifications
You must be signed in to change notification settings - Fork 27.5k
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
node-fetch dependency is outdated #33556
Comments
Another vulnerability could possibly happen for nanoid (dependency of postcss, which is stuck at 8.2.15 even if I try to add it as a direct dependency of my project) |
Probably soon in stable. Merged in canary #33466 |
They updated from |
Here is the advisory with more information. |
#33556 (comment) is the correct answer. |
This closed issue has been automatically locked because it had no new activity for a month. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you. |
Run
next info
(available from version 12.0.8 and up)This is what I receive from NPM after installing Next.js and run
npm audit
What version of Next.js are you using?
12.0.8
What version of Node.js are you using?
17.4.0
What browser are you using?
Edge
What operating system are you using?
Windows
How are you deploying your application?
Other platform
Describe the Bug
2 high severity vulnerabilities
Expected Behavior
No severity vulnerability
To Reproduce
npm install next
The text was updated successfully, but these errors were encountered: