search

Robert-W / grunt-ftp-push

Deploy files to an FTP server as part of your Grunt workflow.
MIT License
39 stars 14 forks source link

new version #33

Closed yonatanmn closed 9 years ago

yonatanmn commented 9 years ago

hi, not sure what's changed in 0.4.0, but it gives me : 

gyp ERR! configure error
gyp ERR! stack Error: Can't find Python executable "python", you can set the PYTHON env variable.
gyp ERR! stack     at failNoPython (C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\configure.js:103:14)
gyp ERR! stack     at C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\configure.js:64:11
gyp ERR! stack     at Object.oncomplete (evalmachine.<anonymous>:107:15)
gyp ERR! System Windows_NT 6.2.9200
gyp ERR! command "node" "C:\\Program Files\\nodejs\\node_modules\\npm\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild"
gyp ERR! cwd C:\projects\H2Hnew\mgmt\node_modules\grunt-ftp-push\node_modules\jest-cli\node_modules\jsdom\node_modules\contextify
gyp ERR! node -v v0.10.33
gyp ERR! node-gyp -v v1.0.3
gyp ERR! not ok
npm ERR! Windows_NT 6.2.9200
npm ERR! argv "C:\\Program Files\\nodejs\\\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install" "grunt-ftp-push" "-
-save-dev"
npm ERR! node v0.10.33
npm ERR! npm  v2.11.0
npm ERR! code ELIFECYCLE

npm ERR! contextify@0.1.14 install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the contextify@0.1.14 install script 'node-gyp rebuild'.
npm ERR! This is most likely a problem with the contextify package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-gyp rebuild
npm ERR! You can get their info via:
npm ERR!     npm owner ls contextify
npm ERR! There is likely additional logging output above.

0.3.6 works fine

Robert-W commented 9 years ago

Hmm, looks like one of the new dependencies uses node-gyp and Python. I don't have a windows machine which is probably why I didn't see this. I'm guessing either eslint or jest. I'm out at the moment but I'll check in a few hours when I get back, probably just need to remove one of those from package.json

Robert-W commented 9 years ago

Ok this most certainly is due to using the jest-cli. Looks like it has issues with running on windows unless that machine has Python and Visual Studio. There are some articles about this on stack overflow. Use 0.3.6 for now and I'll try to swap out the testing framework for one that works everywhere.

Robert-W commented 9 years ago

Ok just pushed 0.4.1, its now using a different testing framework which does not depend on node-gyp.

yonatanmn commented 9 years ago

Cool, Thanks!