x

npm ERR! 404 '@fortawesome/pro-light-svg-icons@^' is not in this registry

  Andrew Fletcher     published: 22 August 2023         1 minute read

Updating NPM packages using npm update and I'm seeing the following response

npm ERR! code E404
npm ERR! 404 Not Found - GET https://registry.npmjs.org/@fortawesome%2fpro-light-svg-icons - Not found
npm ERR! 404
npm ERR! 404  '@fortawesome/pro-light-svg-icons@^5.11.2' is not in this registry.
npm ERR! 404
@fortawesome:registry=https://npm.fontawesome.com/
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: /Users/yourname/.npm/_logs/2023-08-22T00_23_51_015Z-debug-0.log

 

Solution

To resolve this issue, in your theme directory where the package.json file is located check if .npmrc file exists.  If not, create it

vim .npmrc

Add or check if the following exists

@fortawesome:registry=https://npm.fontawesome.com/
//npm.fontawesome.com/:_authToken={TOKEN}

Replace {TOKEN} with your Font Awesome token value.

 

Related articles

Andrew Fletcher • 09 Oct 2023
npm package management
A summary of Node package commandsShort cut commandsnpm install <package>npm i <package>npm install --save <package>npm i -S <package>npm install --save-dev <package>npm i -D <package>npm install --global <package>npm i -G <package>npm testnpm...
Andrew Fletcher • 25 Mar 2022
npm dependencies and devDependencies
Currently I'm working through an app that has been abandoned by the developers.  The client was getting no response from the dev company, when they asked if I could have a look.  The app hadn't been updated for 18 months.  So of course, a product that hasn't been updated in that...
↑