运行Grunt命令Windows 8

时间:2014-07-04 15:33:46

标签: node.js twitter-bootstrap gruntjs npm

我正在尝试使用

安装Grunt
npm install -g grunt-cli

但是我收到错误我不知道如何解释,我是Grunt和web dev的新手。我确定我有一个有效的npm和node.js安装。 如果有人能够解释下面的npm-debug文件意味着什么和/或我应该做些什么来获得有效的grunt安装,那将非常有帮助。

我正在安装Grunt,因为它用于构建Bootstrap。 很抱歉转储大错误日志,我不确定它有多大意义。

11 verbose addNamed [ 'grunt-cli', '' ]
12 verbose addNamed [ null, '*' ]
13 silly lockFile d63f3d0b-grunt-cli grunt-cli@
14 verbose lock grunt-cli@ C:\Users\Kelsey\AppData\Roaming\npm-cache\d63f3d0b-grunt-cli.lock
15 silly addNameRange { name: 'grunt-cli', range: '*', hasData: false }
16 verbose url raw grunt-cli
17 verbose url resolving [ 'https://registry.npmjs.org/', './grunt-cli' ]
18 verbose url resolved https://registry.npmjs.org/grunt-cli
19 info trying registry request attempt 1 at 10:24:14
20 http GET https://registry.npmjs.org/grunt-cli
21 info retry will retry, error on last attempt: Error: getaddrinfo EAGAIN
22 info trying registry request attempt 2 at 10:24:24
23 http GET https://registry.npmjs.org/grunt-cli
24 info retry will retry, error on last attempt: Error: getaddrinfo EAGAIN
25 info trying registry request attempt 3 at 10:25:24
26 http GET https://registry.npmjs.org/grunt-cli
27 silly lockFile d63f3d0b-grunt-cli grunt-cli@
28 silly lockFile d63f3d0b-grunt-cli grunt-cli@
29 error Error: getaddrinfo EAGAIN
29 error     at errnoException (dns.js:37:11)
29 error     at Object.onanswer [as oncomplete] (dns.js:124:16)
30 error If you need help, you may report this *entire* log,
30 error including the npm and node versions, at:
30 error     <http://github.com/npm/npm/issues>
31 error System Windows_NT 6.2.9200
32 error command "c:\\Program Files\\nodejs\\node.exe" "c:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install" "-g" "grunt-cli"
33 error cwd c:\Users\Kelsey\Documents
34 error node -v v0.10.29
35 error npm -v 1.4.14
36 error syscall getaddrinfo
37 error code EAGAIN
38 error errno EAGAIN
39 verbose exit [ 1, true ]

1 个答案:

答案 0 :(得分:1)

看起来cmd / command shell正在尝试运行权限不足的grunt命令。

以管理员身份启动cmd /命令shell,然后解决问题。

相关问题