ProgrammerAH

Programmer Guide, Tips and Tutorial

Skip to content

How to Solve NPM Error 426 Upgrade Required

ERR! 426 Upgrade Required

Solution:

Update the node version to above 14.18.0.

Then upgrade NPM to the latest version

npm install -g npm@latest
npm config set registry https://registry.npmjs.org/

When I try to publish a new package to npm or try to logout, I get the following error message:

npm ERR! code E426
npm ERR! 426 Upgrade Required


Reason: After October 4, 2021, npm websites and npm registry must use TLS Secure Sockets Layer version 1.2, so you need to upgrade the corresponding version

Beginning October 4, 2021, all connections to npm websites and the npm registry—including for package installation—must use TLS 1.2 or higher.

Source
What I did:
upgrade Node (0) to its current recommended version: 14.18.0 LTSupgrade npm with npm install -g npm@latest
In my case, I had to manually set the registry to use https instead of http as well:
npm config set registry https://registry.npmjs.org/


(0) When using nvm, that’s what you need to do:

nvm install 14.18.0
nvm use 14.18.0
nvm alias default 14.18.0

Link:
https://stackoverflow.com/questions/69448082/err-426-upgrade-required-when-i-interact-with-the-npm-registry

This entry was posted in Linux and tagged git, javascript, node.js, NPM Error 426, NPM login on 2021-10-09 by Robins.

Post navigation

← Maven compiles Scala and reports an error stackoverflowerror How to Solve Oracle startup monitoring error →

Recent Posts

  • MAFIA: 1- OpenFlow statistics (Counters, Timestamps)(mafia-sdn/p4demos/demos/1-openflow/1.1-statistics/p4src/of.p4)
  • LDSC: Could not open Corces_ATAC_1000Gv3_ldscores/Corces_ATAC.1.1.l2.ldscore[./gz/bz2]
  • Gradle Package Project Lombok Not Working: No serializer found for class com.qbb.User and no properties discovered to create BeanSerializer……
  • [Solved] PCH Warning: header stop not at file scope
  • pymysql Error: File “/usr/local/lib/python2.7/site-packages/PyMySQL-1.0.2-py2.7.egg/pymysql/connections.py”, line 167 SyntaxError: invalid syntax
Proudly powered by WordPress