npm Community Forum (Archive)

The npm community forum has been discontinued.

To discuss usage of npm, visit the GitHub Support Community.

node is not an internal or external command, nor is it a runnable program or batch files

What I Wanted to Do

npm and node environment has been set correct.

i can use npm -v and node -v command.

but when i user npm start, it comes out error which “node is not an internal or external command, nor is it a runnable program or batch files”

What Happened Instead

Reproduction Steps

Details

here is the error log:

0 info it worked if it ends with ok

1 verbose cli [ ‘D:\nodejs\node.exe’,

1 verbose cli ‘D:\nodejs\node_modules\npm\bin\npm-cli.js’,

1 verbose cli ‘start’ ]

2 info using npm@6.4.1

3 info using node@v10.14.1

4 verbose run-script [ ‘prestart’, ‘start’, ‘poststart’ ]

5 info lifecycle houseweb@0.0.0~prestart: houseweb@0.0.0

6 info lifecycle houseweb@0.0.0~start: houseweb@0.0.0

7 verbose lifecycle houseweb@0.0.0~start: unsafe-perm in lifecycle true

8 verbose lifecycle houseweb@0.0.0~start: PATH: D:\nodejs\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;D:\ou\houseweb\houseweb\node_modules.bin;C:\Program Files\Git\mingw64\bin;C:\Program Files\Git\usr\bin;C:\Users\ukinll\bin;C:\Program Files (x86)\Common Files\Oracle\Java\javapath;C:\Program Files\Docker\Docker\Resources\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0;C:\Program Files\Git\cmd;C:\WINDOWS\System32\OpenSSH;C:\Program Files\Microsoft VS Code\bin;%GRADLE_HOME%\bin;D:\Android\jdk\bi;D:\Android\jdk\jre\bin";C:\Program Files\nodejs;D:\nodejs;C:\Users\ukinll\AppData\Local\Microsoft\WindowsApps;C:\Program Files\Microsoft VS Code\bin;C:\Users\ukinll\AppData\Roaming\npm

9 verbose lifecycle houseweb@0.0.0~start: CWD: D:\ou\houseweb\houseweb

10 silly lifecycle houseweb@0.0.0~start: Args: [ ‘/d /s /c’, ‘webpack-dev-server --progress --inline --hot’ ]

11 silly lifecycle houseweb@0.0.0~start: Returned: code: 1 signal: null

12 info lifecycle houseweb@0.0.0~start: Failed to exec start script

13 verbose stack Error: houseweb@0.0.0 start: webpack-dev-server --progress --inline --hot

13 verbose stack Exit status 1

13 verbose stack at EventEmitter.<anonymous> (D:\nodejs\node_modules\npm\node_modules\npm-lifecycle\index.js:301:16)

13 verbose stack at EventEmitter.emit (events.js:182:13)

13 verbose stack at ChildProcess.<anonymous> (D:\nodejs\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14)

13 verbose stack at ChildProcess.emit (events.js:182:13)

13 verbose stack at maybeClose (internal/child_process.js:962:16)

13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:251:5)

14 verbose pkgid houseweb@0.0.0

15 verbose cwd D:\ou\houseweb\houseweb

16 verbose Windows_NT 10.0.17134

17 verbose argv “D:\nodejs\node.exe” “D:\nodejs\node_modules\npm\bin\npm-cli.js” “start”

18 verbose node v10.14.1

19 verbose npm v6.4.1

20 error code ELIFECYCLE

21 error errno 1

22 error houseweb@0.0.0 start: webpack-dev-server --progress --inline --hot

22 error Exit status 1

23 error Failed at the houseweb@0.0.0 start script.

23 error This is probably not a problem with npm. There is likely additional logging output above.

24 verbose exit [ 1, true ]

Platform Info

$ npm --versions

{ houseweb: '0.0.0',
  npm: '6.4.1',
  ares: '1.14.0',
  cldr: '33.1',
  http_parser: '2.8.0',
  icu: '62.1',
  modules: '64',
  napi: '3',
  nghttp2: '1.34.0',
  node: '10.14.1',
  openssl: '1.1.0j',
  tz: '2018e',
  unicode: '11.0',
  uv: '1.23.2',
  v8: '6.8.275.32-node.36',
  zlib: '1.2.11' }

$ node -p process.platform
   win32

thanks for your helps.