关于windows不支持NODE_ENV=development的问题

问题描述:
最近从github上面clone了一个项目后,进行cnpm install 后,进行cnpm run start 启动后,出现如下错误:
关于windows不支持NODE_ENV=development的问题 - rayliwong - Ray博客
 日志如下:
 
   

0 info it worked if it ends with ok
1 verbose cli [ 'C:\\Program Files\\nodejs\\node.exe',
1 verbose cli 'C:\\Users\\ruili.wang\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli 'run',
1 verbose cli 'start' ]
2 info using [email protected]
3 info using [email protected]
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle [email protected]~prestart: [email protected]
6 silly lifecycle [email protected]~prestart: no script for prestart, continuing
7 info lifecycle [email protected]~start: [email protected]
8 verbose lifecycle [email protected]~start: unsafe-perm in lifecycle true
9 verbose lifecycle [email protected]~start: PATH: C:\Users\ruili.wang\AppData\Roaming\npm\node_modules\npm\bin\node-gyp-bin;E:\web\precise-care-manager-webapp\node_modules\.bin;C:\Users\ruili.wang\bin;D:\Program Files\Git\mingw64\bin;D:\Program Files\Git\usr\local\bin;D:\Program Files\Git\usr\bin;D:\Program Files\Git\usr\bin;D:\Program Files\Git\mingw64\bin;D:\Program Files\Git\usr\bin;C:\Users\ruili.wang\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;D:\Program Files\Git\cmd;D:\Program Files\TortoiseSVN\bin;C:\Program Files\Microsoft Windows Performance Toolkit;C:\v7.5.0\node.exe;C:\Users\ruili.wang\AppData\Roaming\nvm;C:\Program Files\nodejs;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn;C:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn;C:\Python27;C:\Program Files (x86)\Windows Kits\8.1\Windows Performance Toolkit;C:\Program Files\Microsoft SQL Server\110\Tools\Binn;C:\Program Files\nodejs;C:\Users\ruili.wang\AppData\Roaming\npm;D:\Program Files\Git\usr\bin\vendor_perl;D:\Program Files\Git\usr\bin\core_perl
10 verbose lifecycle [email protected]~start: CWD: E:\web\precise-care-manager-webapp
11 silly lifecycle [email protected]~start: Args: [ '/d /s /c', 'NODE_ENV=development webpack-dev-server' ]
12 silly lifecycle [email protected]~start: Returned: code: 1 signal: null
13 info lifecycle [email protected]~start: Failed to exec start script
14 verbose stack Error: [email protected] start: `NODE_ENV=development webpack-dev-server`
14 verbose stack Exit status 1
14 verbose stack at EventEmitter.<anonymous> (C:\Users\ruili.wang\AppData\Roaming\npm\node_modules\npm\lib\utils\lifecycle.js:283:16)
14 verbose stack at emitTwo (events.js:106:13)
14 verbose stack at EventEmitter.emit (events.js:194:7)
14 verbose stack at ChildProcess.<anonymous> (C:\Users\ruili.wang\AppData\Roaming\npm\node_modules\npm\lib\utils\spawn.js:40:14)
14 verbose stack at emitTwo (events.js:106:13)
14 verbose stack at ChildProcess.emit (events.js:194:7)
14 verbose stack at maybeClose (internal/child_process.js:899:16)
14 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
15 verbose pkgid [email protected]
16 verbose cwd E:\web\precise-care-manager-webapp
17 verbose Windows_NT 6.1.7601
18 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\ruili.wang\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js" "run" "start"
19 verbose node v7.8.0
20 verbose npm v5.0.4
21 error code ELIFECYCLE
22 error errno 1
23 error [email protected] start: `NODE_ENV=development webpack-dev-server`
23 error Exit status 1
24 error Failed at the [email protected] start script.
24 error This is probably not a problem with npm. There is likely additional logging output above.
25 verbose exit [ 1, true ]


刚开始以为是npm版本的问题,结果更新npm为最新版本后还是不行,在网上查了一天的资料。第二天突然想着把package.json里面的
 
   

"start": "NODE_ENV=development webpack-dev-server",

改成
 
   

"start": "webpack-dev-server",

结果神奇般的可以启动起来了,然后上网查了一下资料又问了一下同事,发现是windows不支持NODE_ENV=development的问题;
解决方案:
1、通过cnpm install -s cross-env安装cross-env包
2、在 NODE_ENV=development前面加上cross-env,如下所示
 
   

"start": "cross-env NODE_ENV=development webpack-dev-server"

3、重新启动项目就可以了




猜你喜欢

转载自blog.csdn.net/abcwangruili/article/details/77411626