Windows 32bit fail on install

[ArcaneMainFrame]

running this from npm install yields this error on Windows 7 32bit. I can reproduce this error on two separate computers. Any insight as to what may be causing this?

It fails on node-sass@0.8.3 install

node build.js
Error: Cannot find module 'C:\build.js'
Exit Status 0
Failed at the node@-0.8.3 install script

here is the debug read out from where the error starts:

2520 verbose rebuildBundles 'optimist' ]
2521 info install node-sass@0.8.3
2522 verbose unsafe-perm in lifecycle true
2523 info node-sass@0.8.3 Failed to exec install script
2524 info C:\test\node_modules\node-sass unbuild
2525 info preuninstall node-sass@0.8.3
2526 info uninstall node-sass@0.8.3
2527 verbose true,C:\test\node_modules,C:\test\node_modules unbuild node-sass@0.8.3
2528 verbose C:\test\node_modules.bin,[object Object] binRoot
2529 info postuninstall node-sass@0.8.3
2530 error node-sass@0.8.3 install: node build.js
2530 error Exit status 8
2531 error Failed at the node-sass@0.8.3 install script.
2531 error This is most likely a problem with the node-sass package,
2531 error not with npm itself.
2531 error Tell the author that this fails on your system:
2531 error node build.js
2531 error You can get their info via:
2531 error npm owner ls node-sass
2531 error There is likely additional logging output above.
2532 error System Windows_NT 6.1.7601
2533 error command "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "install" "node-sass"
2534 error cwd C:\test
2535 error node -v v0.10.24
2536 error npm -v 1.3.21
2537 error code ELIFECYCLE
2538 verbose exit [ 1, true ]

[andrew]

cc @LaurentGoderre

[LaurentGoderre]

Strange. I don't get that for Windows x64.

[LaurentGoderre]

Looks like I have a VM for 32bit, investigating.

[nschonni]

Can't reproduce it on Vista 32bit in either Bash or command prompt. I did notice a weird path issue when I had "node_modules" folder above where I ran the install command.
EX:

c:\github\
  node_modules\
  test\

Running npm install node-sass in test would run part of it in the context of github\node_modules.

[LaurentGoderre]

I'm also unable to reproduce in Win7 32 bit.

[LaurentGoderre]

@andrew perhaps different install configuration can yield different results.

[LaurentGoderre]

I'm wondering what would happen if we changed the package.json install command to node ./build.js

[LaurentGoderre]

@ArcaneMainFrame acn you try this? npm install https://github.com/LaurentGoderre/node-sass/tarball/fix-256

[LaurentGoderre]

@Quintinius can you try the previous command as well?

[ArcaneMainFrame]

I am still receiving the same error when installing. If it helps looking through the over issue #184 comments you can install it on -force and the plugin works perfectly fine.

2070 verbose rebuildBundles node-sass@0.8.3
2071 verbose rebuildBundles [ '.bin',
2071 verbose rebuildBundles 'chalk',
2071 verbose rebuildBundles 'mkdirp',
2071 verbose rebuildBundles 'mocha',
2071 verbose rebuildBundles 'nan',
2071 verbose rebuildBundles 'node-watch',
2071 verbose rebuildBundles 'optimist' ]
2072 info install node-sass@0.8.3
2073 verbose unsafe-perm in lifecycle true
2074 info node-sass@0.8.3 Failed to exec install script
2075 info C:\test\node_modules\node-sass unbuild
2076 info preuninstall node-sass@0.8.3
2077 info uninstall node-sass@0.8.3
2078 verbose true,C:\test\node_modules,C:\test\node_modules unbuild node-sass@0.8.3
2079 verbose C:\test\node_modules.bin,[object Object] binRoot
2080 info postuninstall node-sass@0.8.3
2081 error node-sass@0.8.3 install: node ./build.js
2081 error Exit status 8
2082 error Failed at the node-sass@0.8.3 install script.
2082 error This is most likely a problem with the node-sass package,
2082 error not with npm itself.
2082 error Tell the author that this fails on your system:
2082 error node ./build.js
2082 error You can get their info via:
2082 error npm owner ls node-sass
2082 error There is likely additional logging output above.
2083 error System Windows_NT 6.1.7601
2084 error command "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "install" "https://github.com/LaurentGoderre/node-sass/tarball/fix-256"
2085 error cwd C:\test
2086 error node -v v0.10.24
2087 error npm -v 1.3.21
2088 error code ELIFECYCLE
2089 verbose exit [ 1, true ]

The debug log is still showing the unsafe perm error.

[nschonni]

I'm curious what test is failing, since they rebuild shouldn't be triggered unless the pre-test fails.

[LaurentGoderre]

I believe the script is run regardless

[LaurentGoderre]

This is very weird. It worked the first time, now it wont work anymore....

[LaurentGoderre]

@ArcaneMainFrame @Quintinius it seems like it might be caused by a corrupted npm dependency. From my VM which was failling, I ran npm install node-sass --force which worked I then uninstalled it and reinstalled without the --force flag and it worked.

Npm has had issues in the past few days which could explain this. Can we close this?

[ArcaneMainFrame]

@LaurentGoderre that doesn't solve the issue either. Though looking for this build.js file it is referencing it seems the plugin or npm, I can't tell which is in control of this, is looking for the build.js file in the C:/ and not where NPM/Node installs globally on the Windows machine. Moving the build.js out of NPM's folder to the C:/ got it past the build error and moved it to a different error still looking for these files in the C:/ directory instead of nodejs/npm/lib where they live.

[LaurentGoderre]

Hmmm, perhaps those were unrelated problems then. back to investigating.

[LaurentGoderre]

@ArcaneMainFrame would it be possible to give me some details about the paths where you run the failing command?

[LaurentGoderre]

Also, just to be sure, can you run node --version?

[nschonni]

The version is 0.10.24 from the end of the log (2086 error node -v v0.10.24)

[ArcaneMainFrame]

The project is contained here in the folder structure: C:\Test
NPM and Node are installed here: NodeJS/NPM & C:\Users\Username\AppData\Roaming\npm
The two directories are where the nodejs.msi on Node's site installs them when you request it installs globally.

But I have tried other various paths when trying to install this and short of me trying to install it within the node folder it always fails on that line.

[LaurentGoderre]

Did you try to install locally or globally?

[ArcaneMainFrame]

Locally

[LaurentGoderre]

I tried many ways to reproduce it without luck

[LaurentGoderre]

This is a similar issue and the fix was to uninstall node and re-install the newest version. Can you try that?

bower/bower#134

[XhmikosR]

I can't reproduce this either in a Windows 7 32bit VM.

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\xmr\Desktop>node -v && npm -v
v0.10.26
1.4.3

[ArcaneMainFrame]

The issue ended up being that if you change the default path in command line from C:\User\Username in regedit to C:\ it starts failing. By changing the path back to the default everything started working again. Thanks to everyone for helping with this.