question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

NODE_PATH not recognized at npm start

See original GitHub issue

As insctructed, I cloned from git and installed the dependencies through npm install. Running ‘npm start’ gets me this error, every time. It somehow seems to take NODE_PATH as a command and not a variable. I’m running Windows 7.

$ npm start

> nodejs-express-mongoose-demo@4.0.0 start c:\development\node-express-mongoose-
demo
> NODE_PATH=./config:./app/controllers NODE_ENV=development ./node_modules/.bin/
nodemon server.js

'NODE_PATH' não é reconhecido como um comando interno ou externo,
programa operacional ou ficheiro batch.

npm ERR! Windows_NT 6.1.7601
npm ERR! argv "c:\\Program Files\\nodejs\\node.exe" "c:\\Program Files\\nodejs\\
node_modules\\npm\\bin\\npm-cli.js" "start"
npm ERR! node v0.10.35
npm ERR! npm  v2.7.4
npm ERR! code ELIFECYCLE
npm ERR! nodejs-express-mongoose-demo@4.0.0 start: `NODE_PATH=./config:./app/con
trollers NODE_ENV=development ./node_modules/.bin/nodemon server.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the nodejs-express-mongoose-demo@4.0.0 start script 'NODE_PAT
H=./config:./app/controllers NODE_ENV=development ./node_modules/.bin/nodemon se
rver.js'.
npm ERR! This is most likely a problem with the nodejs-express-mongoose-demo pac
kage,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     NODE_PATH=./config:./app/controllers NODE_ENV=development ./node_mo
dules/.bin/nodemon server.js
npm ERR! You can get their info via:
npm ERR!     npm owner ls nodejs-express-mongoose-demo
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     c:\development\node-express-mongoose-demo\npm-debug.log

PS: The eight line reads in portuguese “‘NODE_PATH’ is not recognized as an internal or external command, operational program or batch file”.

Issue Analytics

  • State:closed
  • Created 8 years ago
  • Comments:8 (1 by maintainers)

github_iconTop GitHub Comments

6reactions
madhumscommented, May 3, 2017

Take a look at cross-env

0reactions
sfranchicommented, Mar 15, 2018

@madhums cross-env saved my life on Windows… Thanks! 😃

Read more comments on GitHub >

github_iconTop Results From Across the Web

'NODE_PATH' is not recognized as an internal or external ...
When I run npm start command from project directory. I get 'NODE_PATH' is not recognized as an internal or external command, operable program...
Read more >
'Node' Is Not Recognized As An Internal Or External ...
Open up a command line console as an administrator and type the following (assuming this is your path to node). SET PATH=C:\Program Files\Nodejs...
Read more >
How to resolve 'node' is not recognized as an internal or ...
Open the Environment Variables option in your Control Panel. (Go to Control Panel -> System and Security ->System -> Advanced System Settings-> ...
Read more >
Solving node is not recognized as an internal or external ...
Open the command line and type, assuming this is your original path, “SET PATH=C:\Program Files\Nodejs;%PATH%”. So these are a few ways to avoid ......
Read more >
start-server-and-test - npm
To execute all tests simply run npm run ci . Commands. In addition to using NPM script names, you can pass entire commands...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found