Hello, Lothiraldan, I can't compile npm

[net592]

My environment
[root@hdfs02 saltpad]# node -v
v0.10.42
[root@hdfs02 saltpad]# npm -v
3.7.2
[root@hdfs02 saltpad]# cat /etc/redhat-release
CentOS release 6.5 (Final)

Try to test, and failure
**[root@hdfs02 saltpad]# npm install **
saltpad@ /opt/saltpad
├── UNMET PEER DEPENDENCY browserify@>=3.28.0 <=4.x
├─┬ [email protected]
│ └─┬ [email protected]
│ └─┬ [email protected]
│ ├── [email protected]
│ └── [email protected]
└─┬ [email protected]
└─┬ [email protected]
└─┬ [email protected]
└─┬ [email protected]
└─┬ [email protected]
└─┬ [email protected]
└─┬ [email protected]
└─┬ [email protected]
└─┬ [email protected]
└─┬ [email protected]
└─┬ [email protected]
└── [email protected]

npm WARN optional Skipping failed optional dependency /chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture: [email protected]
npm WARN [email protected] requires a peer of browserify@>=3.28.0 <=4.x but none was installed.
npm WARN saltpad@ No license field.

[root@hdfs02 saltpad]# npm start
[573] ./app/services/auto_updater.js 2.43 kB {0} [built]

ERROR in ./~/css-loader!./app/assets/css/style-responsive.css
Module build failed: ReferenceError: Promise is not defined
at LazyResult.async (/opt/saltpad/node_modules/postcss/lib/lazy-result.js:157:31)
at LazyResult.then (/opt/saltpad/node_modules/postcss/lib/lazy-result.js:79:21)
at processCss (/opt/saltpad/node_modules/css-loader/lib/processCss.js:198:5)
at Object.module.exports (/opt/saltpad/node_modules/css-loader/lib/loader.js:24:2)
@ ./app/assets/css/style-responsive.css 4:14-93 13:2-17:4 14:20-99

node.js version ?
A novice...., thank you for your project!

[Lothiraldan]

Could you try with a more recent version of node?

You don't need to install node, npm, node dependency and bower dependency if you just want to test saltpad, you only need to launch the vagrant image located in vagrant directory.

[Lothiraldan]

I think you hit this bug: webpack-contrib/css-loader#144

[net592]

Thank you very much，I try 0.12.x @Lothiraldan

[Lothiraldan]

Any news @net592? If it worked, could you please close the issue?

[Lothiraldan]

@net592 Someone else hit the same bug, did installing a new version of node helped?