Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Not installing on Win7 #15

Open
F1LT3R opened this issue May 3, 2012 · 11 comments
Open

Not installing on Win7 #15

F1LT3R opened this issue May 3, 2012 · 11 comments

Comments

@F1LT3R
Copy link

F1LT3R commented May 3, 2012

I get the following output when I try and install docco-husky in Windows:

c:\Program Files\nodejs\node_modules>npm install -g docco-husky
npm http GET https://registry.npmjs.org/docco-husky
npm http 304 https://registry.npmjs.org/docco-husky
npm http GET https://registry.npmjs.org/dox/0.1.2
npm http GET https://registry.npmjs.org/gravatar/1.0.3
npm http GET https://registry.npmjs.org/walk/2.0.2
npm http GET https://registry.npmjs.org/underscore
npm http GET https://registry.npmjs.org/jade/0.17.0
npm http GET https://registry.npmjs.org/coffee-script
npm http 304 https://registry.npmjs.org/dox/0.1.2
npm http 304 https://registry.npmjs.org/coffee-script
npm http 304 https://registry.npmjs.org/underscore
npm http 304 https://registry.npmjs.org/gravatar/1.0.3
npm http 304 https://registry.npmjs.org/walk/2.0.2
npm http 304 https://registry.npmjs.org/jade/0.17.0
npm http GET https://registry.npmjs.org/forEachAsync
npm http GET https://registry.npmjs.org/commander
npm http GET https://registry.npmjs.org/github-flavored-markdown
npm http GET https://registry.npmjs.org/mkdirp
npm http 304 https://registry.npmjs.org/commander
npm http 304 https://registry.npmjs.org/forEachAsync
npm http 304 https://registry.npmjs.org/github-flavored-markdown
npm http 304 https://registry.npmjs.org/mkdirp
npm http GET https://registry.npmjs.org/sequence
npm http 304 https://registry.npmjs.org/sequence
C:\Users\F1LT3R\AppData\Roaming\npm\docco-husky -> C:\Users\F1LT3R\AppData\Roaming\npm\node_modules\docco-husky\bin\generate

docco-husky@0.3.3 install C:\Users\F1LT3R\AppData\Roaming\npm\node_modules\docco-husky
scripts/install.sh

'scripts' is not recognized as an internal or external command,
operable program or batch file.

npm ERR! docco-husky@0.3.3 install: scripts/install.sh
npm ERR! cmd "/c" "scripts/install.sh" failed with 1
npm ERR!
npm ERR! Failed at the docco-husky@0.3.3 install script.
npm ERR! This is most likely a problem with the docco-husky package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! scripts/install.sh
npm ERR! You can get their info via:
npm ERR! npm owner ls docco-husky
npm ERR! There is likely additional logging output above.
npm ERR!
npm ERR! System Windows_NT 6.1.7600
npm ERR! command "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "install" "-g" "docco-husky"
npm ERR! cwd c:\Program Files\nodejs\node_modules
npm ERR! node -v v0.6.16
npm ERR! npm -v 1.1.19
npm ERR! code ELIFECYCLE
npm ERR! message docco-husky@0.3.3 install: scripts/install.sh
npm ERR! message cmd "/c" "scripts/install.sh" failed with 1
npm ERR! errno {}
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! c:\Program Files\nodejs\node_modules\npm-debug.log
npm not ok

@macguffin
Copy link

Hi did you ever find a solution to this? I am getting the same error message.

Cheers

@fiveisprime
Copy link

+1 any update to this?

@james-gardner
Copy link

+1

@szabyg
Copy link

szabyg commented Oct 9, 2012

+2 -> fallback to docco :-(

@LoicGombeaud
Copy link

+1

@mallim
Copy link

mallim commented May 8, 2013

Can we remove the install.sh? And just allow the installation to continue?

@mallim
Copy link

mallim commented May 8, 2013

groc works although it has the same dependencies

@ghost
Copy link

ghost commented Aug 28, 2013

+1

2 similar comments
@gidor
Copy link

gidor commented Aug 31, 2013

+1

@givankin
Copy link

+1

@daddywoodland
Copy link

I think the following change in package.json will resolve the problem but I'm not able to try it out.

From

"scripts": {
    "install": "scripts/install.sh"
  },

To

"scripts": {
    "install": "node scripts/install.sh"
  },

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

10 participants