-
Notifications
You must be signed in to change notification settings - Fork 1.3k
node-sass@1.0.1: [Windows Error ] %1 is not a valid win32 application #468
Comments
Full Log, Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\Users\Subash>npm install node-sass
-
> node-sass@1.0.1 install C:\Users\Subash\node_modules\node-sass
> node build.js
`win32-x64-v8-3.14` exists; testing
C:\Users\Subash\node_modules\node-sass>node "C:\Program Files\nodejs\node_module
s\npm\bin\node-gyp-bin\\..\..\node_modules\node-gyp\bin\node-gyp.js" rebuild
gyp ERR! configure error
gyp ERR! stack Error: Can't find Python executable "python", you can set the PYT
HON env variable.
gyp ERR! stack at failNoPython (C:\Program Files\nodejs\node_modules\npm\nod
e_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_modu
les\\node-gyp\\bin\\node-gyp.js" "rebuild"
gyp ERR! cwd C:\Users\Subash\node_modules\node-sass
gyp ERR! node -v v0.10.32
gyp ERR! node-gyp -v v1.0.1
gyp ERR! not ok
Build failed
npm ERR! node-sass@1.0.1 install: `node build.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the node-sass@1.0.1 install script.
npm ERR! 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 build.js
npm ERR! You can get their info via:
npm ERR! npm owner ls node-sass
npm ERR! There is likely additional logging output above.
npm ERR! System Windows_NT 6.2.9200
npm ERR! command "C:\\Program Files\\nodejs\\\\node.exe" "C:\\Program Files\\nod
ejs\\node_modules\\npm\\bin\\npm-cli.js" "install" "node-sass"
npm ERR! cwd C:\Users\Subash
npm ERR! node -v v0.10.32
npm ERR! npm -v 1.4.28
npm ERR! code ELIFECYCLE
npm ERR! not ok code 0
C:\Users\Subash>node
> require('node-sass')
Error: Cannot find module 'node-sass'
at Function.Module._resolveFilename (module.js:338:15)
at Function.Module._load (module.js:280:25)
at Module.require (module.js:364:17)
at require (module.js:380:17)
at repl:1:2
at REPLServer.self.eval (repl.js:110:21)
at Interface.<anonymous> (repl.js:239:12)
at Interface.emit (events.js:95:17)
at Interface._onLine (readline.js:202:10)
at Interface._line (readline.js:531:8)
>
(^C again to quit)
>
C:\Users\Subash>npm install node-sass --ignore-scripts
node-sass@1.0.1 node_modules\node-sass
├── get-stdin@3.0.0
├── object-assign@1.0.0
├── node-watch@0.3.4
├── nan@1.3.0
├── shelljs@0.3.0
├── yargs@1.3.2
├── mkdirp@0.5.0 (minimist@0.0.8)
├── chalk@0.5.1 (escape-string-regexp@1.0.2, ansi-styles@1.1.0, supports-color@0
.2.0, strip-ansi@0.3.0, has-ansi@0.1.0)
├── sinon@1.10.3 (util@0.10.3, formatio@1.0.2)
└── mocha@1.21.5 (escape-string-regexp@1.0.2, diff@1.0.8, growl@1.8.1, commander
@2.3.0, jade@0.26.3, glob@3.2.3, debug@2.0.0)
C:\Users\Subash>node
> require('node-sass')
Error: %1 is not a valid Win32 application.
C:\Users\Subash\node_modules\node-sass\bin\win32-x64-v8-3.14\binding.node
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
at Module.require (module.js:364:17)
at require (module.js:380:17)
at requireBinding (C:\Users\Subash\node_modules\node-sass\sass.js:18:14)
at Object.<anonymous> (C:\Users\Subash\node_modules\node-sass\sass.js:25:15)
at Module._compile (module.js:456:26)
at Object.Module._extensions..js (module.js:474:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
> process.versions
{ http_parser: '1.0',
node: '0.10.32',
v8: '3.14.5.9',
ares: '1.9.0-DEV',
uv: '0.10.28',
zlib: '1.2.3',
modules: '11',
openssl: '1.0.1i' }
> |
|
It should and it used to work. If i am not wrong, npm install already installs the latest prebuilt binary for latest node. |
I still see this error on windows 7 64-bit when using latest grunt-sass npm package. Here is what I see in Node console:
|
Please follow the steps in our troubleshooting guide and paste the output
|
I have the same problem, which is fixed by reinstalling the node-sass. |
@Subash you are installing ancient version of node-sass, the current version is node-sass@3.3.3 |
I'm having the same issue and I'm using node 5.6.0 and node-sass 3.8.7 on Windows 7 64 Bit with visual studio 15. "Restore packages" did not work. Here's the current output:
What is causing this error? |
What is the reason for the error |
This issue stopped happening after after installing es6-promise. I've added this line on gulpfile.js
right after
|
I have met this problem before. Or you can try |
@daisyHawen yay, you are right, I had the same issue and I reinstall local |
@daisyHawen Thanks, it works |
after replace the python 3.6.0 to 2.7.0 it's ok |
@Subash it is Ok |
thanks.it is OK |
win7 64 node7.9 |
Issue is here there is a file named %ur proj path%\node_modules\node-sass\vendor\win32-x64-48\binding |
The text was updated successfully, but these errors were encountered: