When i ran sudo npm install -g #ionic/cli
then i got this message:
npm WARN deprecated formidable#1.2.6: Please upgrade to latest,
formidable#v2 or formidable#v3! Check these notes:
https://github.com/node-formidable/formidable/blob/master/VERSION_NOTES.md
changed 212 packages, and audited 213 packages in 35s
26 packages are looking for funding run npm fund for details
found 0 vulnerabilities
then i tryed with "npm install formidable#latest" and "npm install formidable#v2" and "npm install formidable#v3" without solution.
i recived the next message:
robinsonalvarez#MBP-de-Madeline ~ % sudo npm install formidable#v2
up to date, audited 218 packages in 554ms
28 packages are looking for funding run npm fund for details
found 0 vulnerabilities
finally i could't update or install a new formidable version
Had the same issue here..
If you require formidable in your project, you can do an npm install formidable#v2
If you have other packages that require formidable as a dependency, You may want to check the package with npm ls formidable and then troubleshoot if the authors of that package have updated their dependency to the latest one. Or raise an issue if not
In my case, it was chai-http and as on now they still have an open PR to update the projects dependencies.
Related
Whenever I run the command npm install package-name, it doesn't show any error and it also does not install the package(no node_modules folder, just does nothing). Here is the kind of message I get:
up to date, audited 248 packages in 11s
8 packages are looking for funding run npm fund for details
19 vulnerabilities (6 moderate, 9 high, 4 critical)
To address issues that do not require attention, run: npm audit fix
To address all issues (including breaking changes), run: npm audit
fix --force
Run npm audit for details.
I have also tried npm i package-name and npm install --save package-name, but all give the same message. I'm currently using Node version 18.12.1.
What could I be doing wrong and what could be causing this issue?
In order to install npm packages locally, you should run the
npm init
command first.
A file called package.json will be created which contains basic information about the project and the dependencies used in it.
Then in the same directory run the installation command.
Silly me. The fix was to initialize npm in the folder. I ran npm init -y and everything works fine now.
Hi there I'm having some problem with create-react-app:
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
npm WARN deprecated svgo#1.3.2: This SVGO version is no longer supported. Upgrade to v2.x.x.
added 1376 packages, and audited 1377 packages in 22m
181 packages are looking for funding
run npm fund for details
6 moderate severity vulnerabilities
To address all issues, run:
npm audit fix
Run npm audit for details.
A template was not provided. This is likely because you're using an outdated version of create-react-app.
Please note that global installs of create-react-app are no longer supported.
You can fix this by running npm uninstall -g create-react-app or yarn global remove create-react-app before using create-react-app again.
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
I have tried the recomendation steps from the create-react-app official website:
npm uninstall -g create-react-app - This didn't work.
I have clear the npm cache, also didn't work.
I have search with 'where create-react-app' so I can delete it, and it didn't fine anything.
Can anybody help me with this problem? Thank you very much.
The solution I found, after trying lots similar answers was the following:
npm uninstall -g create-react-app
npm cache clean --force
npx create-react-app#latest your-app-name
Notice the "#latest" create-react-app.
Hope it helps
I am simply trying to update webpack-dev-server from version 3.11.2 to the latest version, which is 4.7.3 based on my npm outdated command:
root#fdaf6460fe1a:/home/ubuntu/myapp# npm outdated
Package Current Wanted Latest Location Depended by
#rails/activestorage 6.1.4 6.1.4 7.0.1 node_modules/#rails/activestorage myapp
#rails/ujs 6.1.4 6.1.4 7.0.1 node_modules/#rails/ujs myapp
#rails/webpacker 5.4.0 5.4.0 5.4.3 node_modules/#rails/webpacker myapp
bootstrap 4.3.1 4.3.1 5.1.3 node_modules/bootstrap myapp
datatables.net-bs4 3.2.2 3.2.2 1.11.4 node_modules/datatables.net-bs4 myapp
webpack 4.46.0 4.46.0 5.67.0 node_modules/webpack myapp
webpack-cli 3.3.12 3.3.12 4.9.2 node_modules/webpack-cli myapp
webpack-dev-server 3.11.2 3.11.2 4.7.3 node_modules/webpack-dev-server myapp
However, whenever I run npm update webpack-dev-server, it seems to run but doesn't change the version:
root#fdaf6460fe1a:/home/ubuntu/myapp# npm update webpack-dev-server
up to date, audited 1312 packages in 3s
123 packages are looking for funding
run `npm fund` for details
98 vulnerabilities (2 low, 88 moderate, 8 high)
To address issues that do not require attention, run:
npm audit fix
To address all issues possible (including breaking changes), run:
npm audit fix --force
Some issues need review, and may require choosing
a different dependency.
Run `npm audit` for details.
but when I run npm list webpack-dev-server, the version is still 3.11.2:
root#fdaf6460fe1a:/home/ubuntu/myapp# npm list webpack-dev-server
app#1.0.0 /home/ubuntu/myapp
└── webpack-dev-server#3.11.2
In my package.json file, it does list webpack-dev-server in the following manner:
"webpack-dev-server": "^3.11.2"
However, I've tried removing the ^ and running npm update webpack-dev-server again still, but no luck. How exactly do I update webpack-dev-server in my case or figure out why it's not updating?
How do I even know that npm update is even working? I can run npm update <anything here> and it doesn't return any errors:
root#fdaf6460fe1a:/home/ubuntu/myapp# npm update npmkerjhtekrhjter
up to date, audited 1312 packages in 3s
npm update will only update to whatever is specified in your package.json. Removing the ^ doesn't make it more lax. It makes it more strict.
To update to 4.x: npm install webpack-dev-server#4
That will install the 4.x version and update package.json (and package-lock.json if you're using that).
In your case, npm udpate isn't going to do anything because all the versions in the Current column are the same as the Wanted column. The Wanted column is what npm update will update to, but there's nothing to update. The Latest column lets you know if there are newer versions than what your package.json permits.
I am trying to install the react app using the code:
sudo npm i -g create-react-app#1.5.2
I keep receiving the following response:
npm WARN deprecated tar#2.2.2: This version of tar is no longer supported, and will not receive security updates. Please upgrade asap.
changed 66 packages, and audited 67 packages in 838ms
1 package is looking for funding
run npm fund for details
2 high severity vulnerabilities
Some issues need review, and may require choosing
a different dependency.
I then proceed to execute: npm install tar#6 -g to install the latest version of tar available and then execute: npm show tar version and it says I am running version 6.1.11 which is currently the latest version. However I keep receiving the same error saying that my tar is outdated.
Any ideas as to how I can resolve this challenge?
This happens because of the create-react-app dependency on a particular (2.2.2) version of tar
This is the dependency path:
create-react-app 1.5.2 > tar-pack 3.4.1 > tar 2.2.2
I found the solution
npm install tar#6 -g
When I'm trying to update npm to 7.20.3 (npm install -g npm#7.20.3), npm throws :
npm ERR! code MODULE_NOT_FOUND
npm ERR! Cannot find module 'agentkeepalive'
npm ERR! Require stack:
npm ERR! - /Users/ShaggyRogers/.nvm/versions/node/v14.16.0/lib/node_modules/npm/node_modules/make-fetch-happen/agent.js
...
In order to quickly fix this error just install or re-install globally agentkeepalive :
npm install -g agentkeepalive --save
Then update npm :
npm install -g npm#7.20.3
UPDATE :
Since June 23 2021, the bug seems to be fixed in v7.17.0 (GitHub issue)
You can first upgrade to v7.17.0:
npm install -g npm#7.17.0
Then upgrade to the last version of npm :
npm install -g npm#7.21.0
or
npm install -g npm#latest
This has been discussed on github
TL;DR;
It has been fixed in npm v7.17.0 and newer. I managed to upgrade from 7.10.0 to 7.21.0 and avoid this error entirely (and not dealing with agentkeepalive) by upgrading first to 7.17.0 and then to 7.21.0.
I do not know how, but this one worked for me:
$ npm --version
7.8.0
$ sudo npm uninstall -g npm
removed 252 packages, and audited 1 package in 586ms
found 0 vulnerabilities
$ sudo npm install -g npm
added 1 package, and audited 206 packages in 1s
11 packages are looking for funding
run `npm fund` for details
found 0 vulnerabilities
$ npm --version
8.17.0
Posting it as the accepted answer has not helped.