I know this is a common issue with Node installations where the node isn't added to the environment paths. I've verified this. Place of employment has it locked up somehow and I am trying to figure out what exactly would be blocking it.
I've installed node successfully, cmd line has admin rights but limited. So I can't run node/npm from command line. So, I side stepped moved onto Git Bash and PowerShell successfully. To keep it limited to Git Bash, I've had to manually add npm packages bower, pm2, mocha, etc. to the env. paths manually from the ../User/../Roaming directory. So in bash I can run things like npm -v, node -v, mocha version etc. I can even install, npm install -g mocha.
Where it gets tricky is when I do npm test (with mocha configured in the package.json) mocha initiates but fails and tells me node isn't recognized as internal or external...
Any ideas?
via Dylan Wright
No comments:
Post a Comment