Friday, 15 April 2011

npm package errors after new instalation of node.js on windows 7 -



npm package errors after new instalation of node.js on windows 7 -

i have problems instaling packages npm, after uninstalling node.js c:\nodejs , installing in programme files\nodejs

i removed folders npm cache , npm appdata folder. using latest official node version site. tried chocolatey bundle nodejs.install...

this uotput console:

c:\users\my\desktop>npm install -g gulp npm err! error: unknown, open 'c:\users\my\appdata\roaming\npm-cache\minimatch\0.3.0\package\package.json' npm err! if need help, may study *entire* log, npm err! including npm , node versions, at: npm err! <http://github.com/npm/npm/issues> npm err! scheme windows_nt 6.1.7601 npm err! command "c:\\program files\\nodejs\\\\node.exe" "c:\\program files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install" "-g" "gulp" npm err! cwd c:\users\my\desktop npm err! node -v v0.10.29 npm err! npm -v 1.4.14 npm err! path c:\users\my\appdata\roaming\npm-cache\minimatch\0.3.0\package\package.json npm err! code unknown npm err! errno -1 npm err! npm err! additional logging details can found in: npm err! c:\users\my\desktop\npm-debug.log npm err! not ok code 0 c:\users\my\desktop>

after trying install gulp installed grunt

c:\users\my\desktop>npm install -g grunt grunt@0.4.5 c:\users\my\appdata\roaming\npm\node_modules\grunt ├── dateformat@1.0.2-1.2.3 ├── which@1.0.5 ├── eventemitter2@0.4.13 ├── getobject@0.1.0 ├── colors@0.6.2 ├── rimraf@2.2.8 ├── async@0.1.22 ├── hooker@0.2.3 ├── grunt-legacy-util@0.2.0 ├── exit@0.1.2 ├── lodash@0.9.2 ├── coffee-script@1.3.3 ├── iconv-lite@0.2.11 ├── underscore.string@2.2.1 ├── minimatch@0.2.14 (sigmund@1.0.0, lru-cache@2.5.0) ├── glob@3.1.21 (inherits@1.0.0, graceful-fs@1.2.3) ├── findup-sync@0.1.3 (lodash@2.4.1, glob@3.2.11) ├── nopt@1.0.10 (abbrev@1.0.5) ├── grunt-legacy-log@0.1.1 (lodash@2.4.1, underscore.string@2.3.3) └── js-yaml@2.0.5 (esprima@1.0.4, argparse@0.1.15) c:\users\my\desktop>

do seek this?: npm cache clear

i solve similar issue command.

windows npm

No comments:

Post a Comment