A while back I upgraded npm to version 5 using
[code lang=text]
npm install -g npm@latest
[/code]
or
[code lang=text]
npm install -g npm@5
[/code]
not really realising that SPFx doesn’t support version 5 of npm (yet). I had to downgrade npm.
running npm install -g npm@3 seemed to be to obvious but that didn’t work:
I tried uninstalling node.js and I tried removing the npm.cmd command mentioned, but all didn’t work.
then I came across the folder C:\Users\myusername\AppData\Roaming with a folder npm and npm-cache
I removed these two folders and then reinstalled node.js. and now npm -v returns the correct version:
Discover more from SharePains
Subscribe to get the latest posts sent to your email.
Pieter Veenstra
Is your business still running on paper trails, sprawling Excel files, or ageing Access databases? There's a better way — and I can show you exactly what it looks like. I'm the Technical Director of Vantage 365, a Microsoft solutions consultancy working with clients across the UK, the Netherlands, and worldwide. For over 30 years I've been turning messy, manual business processes into clean, automated systems that save time, reduce errors, and give teams the visibility they need to make better decisions. SharePains is not just any blog run by a Microsoft MVP. Have you ever used Try-Catch in Power Automate? The original post about Try-Catch in Power Automate can still be found on this site, https://sharepains.com/2018/02/07/try-catch-finally-in-power-automate-flow/ Or have you ever used the Pieter’s method to avoid variables and speed up your flows? https://sharepains.com/2020/03/11/pieters-method-for-advanced-in-flows/ You can contact me using contact@sharepains.com