We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not sure how many of these are my fault/naivete, but I figured I'd list them here in case others ran into them:
Windows path too long issue: nodejs/node#1849 remy/nodemon#559
Workaround (see nodejs/node#1849 (comment) and remy/nodemon#559 (comment)):
npm config set prefix=C:\npm
node_gyp Windows dependencies issue: nodejs/node-gyp#629 https://github.com/nodejs/node-gyp
Gulp install issue: https://stackoverflow.com/questions/24010598/node-js-cannot-find-module-readable-stream
For some reason npm install -g gulp babel didn't work so I did them separately:
npm install -g gulp babel
npm install -g gulp npm install -g babel npm install -g stylus
EPERM error: http://blogs.msdn.com/b/matt-harrington/archive/2012/02/23/how-to-fix-node-js-npm-permission-problems.aspx
I had to run npm cache clean
npm cache clean
Error: Cannot find module 'gulp-stylus'
npm install --save-dev gulp-stylus
Failed to load external module babel-core/register: yeoman/generator-webapp#356 (comment)
npm install --save-dev babel-core
...and after all that: success!
git clone --depth 1 https://github.com/dmnsgn/gulp-frontend-boilerplate.git && cd gulp-frontend-boilerplate && rd /s /q .git npm run init npm install gulp
The text was updated successfully, but these errors were encountered:
...oh, and one more:
npm cache clean && npm install -g napa
Sorry, something went wrong.
P.S. It appears gulp only works if run in a cmd prompt with Administrator privileges
gulp
Thanks for all these tips on using it on Windows! Very helpful. I will see if I can fix some issues.
No branches or pull requests
Not sure how many of these are my fault/naivete, but I figured I'd list them here in case others ran into them:
Windows path too long issue:
nodejs/node#1849
remy/nodemon#559
Workaround (see nodejs/node#1849 (comment) and remy/nodemon#559 (comment)):
npm config set prefix=C:\npm
node_gyp Windows dependencies issue:
nodejs/node-gyp#629
https://github.com/nodejs/node-gyp
Gulp install issue: https://stackoverflow.com/questions/24010598/node-js-cannot-find-module-readable-stream
For some reason
npm install -g gulp babel
didn't work so I did them separately:EPERM error: http://blogs.msdn.com/b/matt-harrington/archive/2012/02/23/how-to-fix-node-js-npm-permission-problems.aspx
I had to run
npm cache clean
Error: Cannot find module 'gulp-stylus'
npm install --save-dev gulp-stylus
Failed to load external module babel-core/register: yeoman/generator-webapp#356 (comment)
npm install --save-dev babel-core
...and after all that: success!
The text was updated successfully, but these errors were encountered: