Open mattezell opened 7 years ago
Downgrade npm/node to 6/7.
@danielsogl, would you happen to know if there's an issue to track support being added for node 8/npm 5? I can't seem to find one. Thank you!
node 8 will be supported?
i have the same problem how can i solve it am using window 10 Node.js 6.11.0 npm 3.
C:\Windows\System32\myApp>npm install npm WARN invalid config proxy="$PROXY" npm WARN invalid config Must be a full url with 'http://' npm WARN invalid config proxy="$PROXY" npm WARN invalid config Must be a full url with 'http://' npm WARN prefer global node-gyp@3.6.2 should be installed with -g
node-sass@4.5.3 install C:\Windows\System32\myApp\node_modules\node-sass node scripts/install.js
Downloading binary from https://github.com/sass/node-sass/releases/download/v4.5.3/win32-x64-48_binding.node Cannot download "https://github.com/sass/node-sass/releases/download/v4.5.3/win32-x64-48_binding.node":
ESOCKETTIMEDOUT
Hint: If github.com is not accessible in your location try setting a proxy via HTTP_PROXY, e.g.
export HTTP_PROXY=http://example.com:1234
or configure npm proxy via
npm config set proxy http://example.com:8080
node-sass@4.5.3 postinstall C:\Windows\System32\myApp\node_modules\node-sass node scripts/build.js
Binary found at C:\Windows\System32\myApp\node_modules\node-sass\vendor\win32-x64-48\binding.node Testing binary Binary has a problem: Error: %1 is not a valid Win32 application. \?\C:\Windows\System32\myApp\node_modules\node-sass\vendor\win32-x64-48\binding.node at Error (native) at Object.Module._extensions..node (module.js:597:18) at Module.load (module.js:487:32) at tryModuleLoad (module.js:446:12) at Function.Module._load (module.js:438:3) at Module.require (module.js:497:17) at require (internal/module.js:20:19) at module.exports (C:\Windows\System32\myApp\node_modules\node-sass\lib\binding.js:19:10) at Object.
(C:\Windows\System32\myApp\node_modules\node-sass\lib\index.js:14:35) at Module._compile (module.js:570:32) Building the binary locally Building: C:\Program Files\nodejs\node.exe C:\Windows\System32\myApp\node_modules\node-gyp\bin\node-gyp.js rebuild --verbose --libsass_ext= --libsass_cflags= --libsass_ldflags= --libsass_library= gyp info it worked if it ends with ok gyp verb cli [ 'C:\Program Files\nodejs\node.exe', gyp verb cli 'C:\Windows\System32\myApp\node_modules\node-gyp\bin\node-gyp.js', gyp verb cli 'rebuild', gyp verb cli '--verbose', gyp verb cli '--libsass_ext=', gyp verb cli '--libsass_cflags=', gyp verb cli '--libsass_ldflags=', gyp verb cli '--libsass_library=' ] gyp info using node-gyp@3.6.2 gyp info using node@6.11.0 | win32 | x64 gyp verb command rebuild [] gyp verb command clean [] gyp verb clean removing "build" directory gyp verb command configure [] gyp verb check python checking for Python executable "python2" in the PATH gyp verb which
failed Error: not found: python2 gyp verbwhich
failed at getNotFoundError (C:\Windows\System32\myApp\node_modules\which\which.js:13:12) gyp verbwhich
failed at F (C:\Windows\System32\myApp\node_modules\which\which.js:68:19) gyp verbwhich
failed at E (C:\Windows\System32\myApp\node_modules\which\which.js:80:29) gyp verbwhich
failed at C:\Windows\System32\myApp\node_modules\which\which.js:89:16 gyp verbwhich
failed at C:\Windows\System32\myApp\node_modules\isexe\index.js:42:5 gyp verbwhich
failed at C:\Windows\System32\myApp\node_modules\isexe\windows.js:36:5 gyp verbwhich
failed at FSReqWrap.oncomplete (fs.js:123:15) gyp verbwhich
failed python2 { Error: not found: python2 gyp verbwhich
failed at getNotFoundError (C:\Windows\System32\myApp\node_modules\which\which.js:13:12) gyp verbwhich
failed at F (C:\Windows\System32\myApp\node_modules\which\which.js:68:19) gyp verbwhich
failed at E (C:\Windows\System32\myApp\node_modules\which\which.js:80:29) gyp verbwhich
failed at C:\Windows\System32\myApp\node_modules\which\which.js:89:16 gyp verbwhich
failed at C:\Windows\System32\myApp\node_modules\isexe\index.js:42:5 gyp verbwhich
failed at C:\Windows\System32\myApp\node_modules\isexe\windows.js:36:5 gyp verbwhich
failed at FSReqWrap.oncomplete (fs.js:123:15) gyp verbwhich
failed stack: 'Error: not found: python2\n at getNotFoundError (C:\Windows\System32\myApp\node_modules\which\which.js:13:12)\n at F (C:\Windows\System32\myApp\node_modules\which\which.js:68:19)\n at E (C:\Windows\System32\myApp\node_modules\which\which.js:80:29)\n at C:\Windows\System32\myApp\node_modules\which\which.js:89:16\n at C:\Windows\System32\myApp\node_modules\isexe\index.js:42:5\n at C:\Windows\System32\myApp\node_modules\isexe\windows.js:36:5\n at FSReqWrap.oncomplete (fs.js:123:15)', gyp verbwhich
failed code: 'ENOENT' } gyp verb check python checking for Python executable "python" in the PATH gyp verbwhich
succeeded python C:\Users\DataMining\AppData\Local\Programs\Python\Python35\python.EXE gyp verb check python versionC:\Users\DataMining\AppData\Local\Programs\Python\Python35\python.EXE -c "import platform; print(platform.python_version());"
returned: "3.5.2\r\n" gyp verb could not find "C:\Users\DataMining\AppData\Local\Programs\Python\Python35\python.EXE". checking python launcher gyp verb could not find "C:\Users\DataMining\AppData\Local\Programs\Python\Python35\python.EXE". guessing location gyp verb ensuring that file exists: C:\Python27\python.exe gyp ERR! configure error gyp ERR! stack Error: Can't find Python executable "C:\Users\DataMining\AppData\Local\Programs\Python\Python35\python.EXE", you can set the PYTHON env variable. gyp ERR! stack at Object.failNoPython (C:\Windows\System32\myApp\node_modules\node-gyp\lib\configure.js:483:19) gyp ERR! stack at Object.(C:\Windows\System32\myApp\node_modules\node-gyp\lib\configure.js:508:16) gyp ERR! stack at C:\Windows\System32\myApp\node_modules\graceful-fs\polyfills.js:284:29 gyp ERR! stack at FSReqWrap.oncomplete (fs.js:123:15) gyp ERR! System Windows_NT 10.0.14393 gyp ERR! command "C:\Program Files\nodejs\node.exe" "C:\Windows\System32\myApp\node_modules\node-gyp\bin\node-gyp.js" "rebuild" "--verbose" "--libsass_ext=" "--libsass_cflags=" "--libsass_ldflags=" "--libsass_library=" gyp ERR! cwd C:\Windows\System32\myApp\node_modules\node-sass gyp ERR! node -v v6.11.0 gyp ERR! node-gyp -v v3.6.2 gyp ERR! not ok Build failed with error code: 1 npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.0.0 (node_modules\chokidar\node_modules\fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.1.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"}) npm ERR! Windows_NT 10.0.14393 npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "install" npm ERR! node v6.11.0 npm ERR! npm v3.10.10 npm ERR! code ELIFECYCLE npm ERR! node-sass@4.5.3 postinstall:
node scripts/build.js
npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the node-sass@4.5.3 postinstall script 'node scripts/build.js'. npm ERR! Make sure you have the latest version of node.js and npm installed. npm ERR! If you do, this is most likely a problem with the node-sass package, npm ERR! not with npm itself. npm ERR! Tell the author that this fails on your system: npm ERR! node scripts/build.js npm ERR! You can get information on how to open an issue for this project with: npm ERR! npm bugs node-sass npm ERR! Or if that isn't available, you can get their info via: npm ERR! npm owner ls node-sass npm ERR! There is likely additional logging output above.npm ERR! Please include the following file with any support request: npm ERR! C:\Windows\System32\myApp\npm-debug.log
npm install -g npm@4.6.1
brew uninstall node
After this you just have to install the version you want to. This can usually be done with brew, although the package/formulae versioning did change recently; something like:
brew install node@6
brew link --force node@6
and fix this bug. i work for me.
I solved this issue by updating ionic-cli & downgrading node & npm. Here is my config:
$ ionic info
cli packages: (/home/qdmb9595/.nvm/versions/node/v6.11.5/lib/node_modules)
@ionic/cli-plugin-proxy : 1.5.6
@ionic/cli-utils : 1.19.0
ionic (Ionic CLI) : 3.19.0
global packages:
cordova (Cordova CLI) : 7.1.0
local packages:
@ionic/app-scripts : 3.1.6
Cordova Platforms : none
Ionic Framework : ionic-angular 3.9.2
System:
Node : v6.11.5
npm : 3.10.10
OS : Linux 4.4
npm install @ionic/app-scripts@latest --save-dev work for me
npm install @ionic/app-scripts@latest --save-dev work for me
Yehh!! work for me tanks
Note: for support questions, please use one of these channels:
https://forum.ionicframework.com/ http://ionicworldwide.herokuapp.com/
Short description of the problem:
"ionic start myApp super" fails during npm install on node-sass@4.5.0 due to 404 on binary download.
What behavior are you expecting?
For "ionic start" to generate an application based on the 'super' template.
Steps to reproduce: