When I run npm i axios I get the following errors:
C:\Users\Mary\star-wars>npm i axios
npm ERR! code E404
npm ERR! 404 Not Found - GET https://skimdb.npmjs.com/registry/axios/-/axios-0.27.2.tgz - not_found
npm ERR! 404
npm ERR! 404 'axios#https://skimdb.npmjs.com/registry/axios/-/axios-0.27.2.tgz' is not in this registry.
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\Mary\AppData\Local\npm-cache_logs\2022-07-07T14_23_38_747Z-debug-0.log
I can´t find anything that works for me, I´ve tried to reinstall dependencies, I´ve tried to unistall axios and re-install it without success.
I´ve checked the log & it contains the same error that shows when I run the command.
Has anyone found a solution for this?
I was finally able to do what I intended by running it as Admin, creating a different folder, running npm cache clean -f and setting npm. registry
After that, everything went smooth.
Related
I'm trying to install packages for an angular project based on a template of the customer.
He has provided me this let's say ready to use template, but when I run npm install I get errors.
npm ERR! code E404
npm ERR! 404 Not Found - GET https://artifactory.springlab.enel.com/artifactory/api/npm/npm-public/#angular-devkit%2fbuild-angular
npm ERR! 404
npm ERR! 404 '#angular-devkit/build-angular#~0.1102.19' is not in this registry.
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git URL.
As you can see the issue is on a GET from a server of theirs. I have highlighted this issue but they said that is not their fault as they can run npm install without any issue.
Please note that:
When I run the npm install I'm logged in inside their VPN to access the servers.
I've tried several versions of node and npm, using the same version that is working on their machines.
I've tried both --force and --legacy-peer-deps and I always get the same error.
I have no issues on npm in any of the other 10s projects I work on (for other customers)
I have also disabled the antivirus.
IT support from the company is not providing me with help, so I'm alone and I don't know what to check.
How can I get more details on why I got a 404 on that?
I'm trying to publish a package to Gitlab package registry but it keeps erroring me with 404 #my-scope/<package-name> is not in this registry.
Initially I followed the instructions in here official docs
This is how my .npmrc looks like:
#my-scope:registry=https://gitlab.com/api/v4/projects/<project_id>/packages/npm/
//gitlab.com/api/v4/projects/<project_id>/packages/npm/:_authToken=${TOKEN}
also I've added publishConfig to package.json
"publishConfig": {
"#my-scope:registry": "https://gitlab.com/api/v4/projects/<project_id>/packages/npm/"
},
When I run npm publish I keep getting 404 error as below.
npm notice Publishing to https://gitlab.com/api/v4/projects/<project_id>/packages/npm/
npm ERR! code E404
npm ERR! 404 Not Found - PUT https://gitlab.com/api/v4/projects/<project_id>/packages/npm/#my-scope%2fpackage-name
npm ERR! 404
npm ERR! 404 '#my-scope/package-name#1.5.0' is not in this registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
npm ERR! 404
npm ERR! 404 Note that you can also install from a
Your .npmrc should looks like this according to the docs:
#foo:registry=https://gitlab.example.com/api/v4/packages/npm/
//gitlab.example.com/api/v4/packages/npm/:_authToken=${MY_TOKEN}
//gitlab.example.com/api/v4/projects/<your_project_id>/packages/npm/:_authToken=${MY_TOKEN}
Read several threads here in SO but haven't found the exact some type of issue. I'm having trouble trying to install a private package from my company (hosted on GitLab). The strangest thing is that I've already made it for the same repo, but inside vagrant. On vagrant, after having receiving the following error on a npm install:
ERR! code E404
npm ERR! 404 Not Found - GET https://registry.npmjs.org/#company-name%2foauth20-provider - Not found
npm ERR! 404
npm ERR! 404 '#company-name/oauth20-provider#0.8.0' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
npm ERR! 404 It was specified as a dependency of 'project-srv'
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\João~1\AppData\Roaming\npm-cache\_logs\2022-02-06T14_38_17_991Z-debug.log
I solved it by following these steps:
1 - Generate a new personal access token on GitLab (scope API): https://gitlab.com/-/profile/personal_access_tokens
2 - Run commands:
npm config set #company-name:registry https://gitlab.com/api/v4/projects/project-id/packages/npm/
npm config set -- '//gitlab.com/api/v4/projects/project-id/packages/npm/:_authToken' "<my-personal-access-token>"
When I try to run npm install outside of vagrant (in the same folder or another clone of the repo), it still gives the 404 error above. The thing is, I'm certain the steps I've tried are valid, since they work inside vagrant. What can possibly change by trying to do npm install outside of vagrant? I believe that it can possibly have to do with the OS, since I'm using the Laravel Homestead vagrant box (i.e. Ubuntu 20.04), and I'm running it on a Windows 10 machine.
I am creating a new electron app and now I need to install electron-packager in it.
node -v v10.16.0 & npm -v v6.9.0
(I updated both)
I have tried to run this:
npm install electron-packager --save-dev
and this:
npm install electron-packager -g
The Error:
npm ERR! code E404
npm ERR! 404 Not Found - GET http://registry.npmjs.org/electron-packager
npm ERR! 404
npm ERR! 404 'electron-packager#latest' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.
What can I do?
Thanks!
It would be better if you specified the OS.
I once faced this problem and downgrading node to v8.0 fixed this problem.
But I would strongly recommend you to use electron-builder(https://github.com/electron-userland/electron-builder) instead of electron-packager for creating installer packages, as it is a lot easier with lot more options including built-in auto-update feature.
I am trying to install protractor but receiving following error.
command:
npm install -g protractor
npm ERR! node v4.4.3
npm ERR! npm v2.15.1
npm ERR! code E404
npm ERR! 404 no such package available : #types/jasmine
npm ERR! 404
npm ERR! 404 '#types/jasmine' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
npm ERR! 404 It was specified as a dependency of 'protractor'
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.
npm ERR! Please include the following file with any support request:
npm ERR! F:\temp\chrome downloads\npm-debug.log
I came across this issue today and my problem was that I had set a custom registry within the npm config file. Have you ever used "npm set registry"?
If so, you can manually tell npm where to look for the '#types' registry with the following command:
npm config set #types:registry https://registry.npmjs.org/
The problem is coming from the fact that you're using a private registry that has not yet added support for #organization packages.
In my case, I was using Sonatype Nexus and my version didn't have support for those types of packages. #Willie Valdez's suggestion is probably the best solution for you, right now.
Also, check if you have a .npmrc file in your home directory or in your project directory. The registry might be there. If that's the case, just rename the file to npmrc_bak or something else until you install the package and then revert back to its original name.
You can also include a .npmrc file in your current project with the below details:
#angular:registry=https://registry.npmjs.org
#types:registry=https://registry.npmjs.org
#ngtools:registry=https://registry.npmjs.org
#angular-cli:registry=https://registry.npmjs.org
its handy and resuable across new projects.