When
Occurs when running npm i on older Angular applications.
Solution
// powershell
$env:NODE_OPTIONS="--openssl-legacy-provider"Update global npm packages
// Updating all globally-installed packages
npm update -g
// or
npm install npm@latest -g
// Determining which global packages need updating
npm outdated -g --depth=0
// Updating a single global package
npm update -g <package_name>Update node via npm
// install this
sudo npm i -g n
// run this command
sudo n latestSELF_SIGNED_CERT_IN_CHAIN
npm config -g set strict-ssl falselist all globally installed npm modules
npm ls -g --depth 0Repository is not clean. Please commit or stash any changes before updating
you can force ng to update anyways using --allow-dirty
ng update --all --allow-dirtyInstall Specific Package Version
npm install [email protected]Update all npm/Angular packages
// npm packages
npm i -g npm-check-updates
ncu -u
npm install
// angular packages
ng update --allbasic angular requirements
// global req.
npm i -g @angular/cliMSBUILD : error MSB3428: Could not load the Visual C++ component “VCBuild.exe”. To fix this, 1) install the .NET Framework 2.0 SDK, 2) install Microsoft Visual Studio 2005 or 3) add the location of the component to the system path if it is installed elsewhere.
npm install -g windows-build-toolsUNABLE_TO_GET_ISSUER_CERT_LOCALLY
npm config set registry http://registry.npmjs.org/