Closed sQVe closed 10 years ago
Might be a case of the Windows environment not able to execute bash commands. I'm not currently able to test this unfortunately, but maybe you could run that command in your shell from your project root and paste the output here.
Is this bash command necessary? Why do we have to run npm install
again for this dependency?
A solution would be to use a postinstall.js which runs on all platforms, same for npm test
:
https://github.com/backflip/customizr/commit/07a0daa744a154758660a1fa00c97fc962bc1469
@doctyper Would you consider a pull-request containing above changes?
Can you make a pull request @backflip? This seems like good, but I prefer keep the main repo as target.
+1 for this :+1:
have same issue. System Windows_NT 6.1.7601 node 0.10.31 npm 1.4.23
I've make Pull Request directly from the @backflip code here : https://github.com/doctyper/customizr/pull/4
Sorry for the delay, @Alex-D.
IMHO, my fork isn't really ready for merging:
I've just pushed an updated build to the develop branch. It moves the inline shell code to a (hopefully) cross-OS-friendly node script. To update:
$ npm uninstall gulp-modernizr
$ npm cache clear
$ npm install --save-dev "gulp-modernizr@https://github.com/doctyper/gulp-modernizr/tarball/develop"
Let me know if this alleviates the errors.
/ht @backflip
Thanks a lot! As mentioned in https://github.com/doctyper/gulp-modernizr/issues/14#issuecomment-61655979 there is still an issue with spawn on Windows, but https://github.com/doctyper/customizr/pull/5 should resolve it.
I'm trying to install this package the following way:
Also by just cloning the rep and then running
npm install
in it.Both ways give me this error:
I'm on Windows, if that makes any difference.
Would love some help or insight on how I could resolve this error, would really love to use your awesome customizr.