Installation issue CentOS

[dligthart]

Installing on CentOS results into the following error:

strider@1.6.0-pre.2 pre /usr/lib/node_modules/strider
mkdirp dist/scripts dist/styles

sh: mkdirp: command not found
npm ERR! weird error 127
npm ERR! not ok code 0
npm ERR! weird error 1
npm ERR! not ok code 0
npm ERR! weird error 1
npm ERR! not ok code 0

[knownasilya]

Mae sure you aren't installing with the --production flag. Other then that, mkdirp is installed when doing npm install, so everything should work. Most likely a bad install, so delete node_modules/ folder and try again.

[dligthart]

strider@1.6.0-pre.2 styles /usr/local/lib/node_modules/strider
lessc client/styles/strider.less > dist/styles/styles.css

sh: 1: lessc: not found

[dligthart]

sudo npm install -g mkdirp
sudo npm install -g strider
sh: 1: lessc: not found
sudo npm install -g less

[dligthart]

sh: 1: browserify: not found

[dligthart]

Error: Cannot find module 'browserify-shim' from '/usr/local/lib/node_modules/strider'
at /usr/local/lib/node_modules/browserify/node_modules/resolve/lib/async.js:50:17
at process (/usr/local/lib/node_modules/browserify/node_modules/resolve/lib/async.js:119:43)
at /usr/local/lib/node_modules/browserify/node_modules/resolve/lib/async.js:128:21
at load (/usr/local/lib/node_modules/browserify/node_modules/resolve/lib/async.js:60:43)
at /usr/local/lib/node_modules/browserify/node_modules/resolve/lib/async.js:66:22
at /usr/local/lib/node_modules/browserify/node_modules/resolve/lib/async.js:21:47
at Object.oncomplete (fs.js:107:15)

[knownasilya]

once again, you need to actually run npm install, those are all modules from npm that need to be installed and are in the package.json.

[dligthart]

Yes but I'm installing strider from the npm.

"sudo npm install -g strider"

Those packages are missing; or for some reason not installed.

After manually installing above missing packages I was able to install the strider npm.

strider@1.6.0-pre.2

[knownasilya]

@dligthart I would not recommend installing strider with -g, because usually there are issues with permissions on linux systems that prevent node from installing those packages properly. The preferred solution is to clone the repository, if you can.

The other solution is here: #650 (comment), which will fix your global installs.

[knownasilya]

Closing, since this is really a duplicate of #650.