Webpack was working fine all day and when I added a new image it suddenly failed. I updated node and npm and I still get the following error. How would I go about fixing this or using an alternative? The other image loader modules I attempted to install give the same error.
74857 verbose stack Error: gifsicle#3.0.4 postinstall: `node lib/install.js`
74857 verbose stack Exit status 1
74857 verbose stack at EventEmitter.<anonymous> (C:\Users\mykod\AppData\Roaming\npm\node_modules\npm\lib\utils\lifecycle.js:279:16)
74857 verbose stack at emitTwo (events.js:106:13)
74857 verbose stack at EventEmitter.emit (events.js:191:7)
74857 verbose stack at ChildProcess.<anonymous> (C:\Users\mykod\AppData\Roaming\npm\node_modules\npm\lib\utils\spawn.js:40:14)
74857 verbose stack at emitTwo (events.js:106:13)
74857 verbose stack at ChildProcess.emit (events.js:191:7)
74857 verbose stack at maybeClose (internal/child_process.js:877:16)
74857 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
74858 verbose pkgid gifsicle#3.0.4
74859 verbose cwd C:\Users\mykod\Desktop\best-voted
74860 error Windows_NT 10.0.14393
74861 error argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\mykod\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js" "install"
74862 error node v6.9.4
74863 error npm v4.3.0
74864 error code ELIFECYCLE
74865 error errno 1
74866 error gifsicle#3.0.4 postinstall: `node lib/install.js`
74866 error Exit status 1
74867 error Failed at the gifsicle#3.0.4 postinstall script 'node lib/install.js'.
74867 error Make sure you have the latest version of node.js and npm installed.
74867 error If you do, this is most likely a problem with the gifsicle package,
74867 error not with npm itself.
74867 error Tell the author that this fails on your system:
74867 error node lib/install.js
74867 error You can get information on how to open an issue for this project with:
74867 error npm bugs gifsicle
74867 error Or if that isn't available, you can get their info via:
74867 error npm owner ls gifsicle
74867 error There is likely additional logging output above.
74868 verbose exit [ 1, true ]
Restarting doesn't help for me. There was problems with permissions on my laptop.
I'm working on Ubuntu 16.04.
Here is solution: fixing npm permissions
I'm recommending to watch video first.
At least check NPM's directory first npm config get prefix and if it's /usr, you have to use Option 2.
I've solved this problems with processing step by step of Option 2.
I restarted my computer and was able to install it. Windows.
Related
So as part of some work I'm doing, I am trying to get the packages we use in our application up to the latest versions as when running npm audit there were a significant amount of vulnerabilities.
One of the the things it comes up saying to install mocha#9.2.2
I have been trying to do this but I get an error saying:
npm ERR! Invalid version: ^6.0.1
I have no idea what this is referring to as in the package.json there are no packages that have this version and when I look at the debug log I just get:
207 verbose stack TypeError: Invalid Version: ^6.0.1
207 verbose stack at new SemVer (C:\Program Files\nodejs\node_modules\npm\node_modules\semver\classes\semver.js:38:13)
207 verbose stack at compare (C:\Program Files\nodejs\node_modules\npm\node_modules\semver\functions\compare.js:3:32)
207 verbose stack at Object.gte (C:\Program Files\nodejs\node_modules\npm\node_modules\semver\functions\gte.js:2:30)
207 verbose stack at CanPlaceDep.checkCanPlaceCurrent (C:\Program Files\nodejs\node_modules\npm\node_modules\#npmcli\arborist\lib\can-place-dep.js:173:51)
207 verbose stack at CanPlaceDep.checkCanPlace (C:\Program Files\nodejs\node_modules\npm\node_modules\#npmcli\arborist\lib\can-place-dep.js:157:27)
207 verbose stack at new CanPlaceDep (C:\Program Files\nodejs\node_modules\npm\node_modules\#npmcli\arborist\lib\can-place-dep.js:114:26)
207 verbose stack at PlaceDep.place (C:\Program Files\nodejs\node_modules\npm\node_modules\#npmcli\arborist\lib\place-dep.js:121:19)
207 verbose stack at new PlaceDep (C:\Program Files\nodejs\node_modules\npm\node_modules\#npmcli\arborist\lib\place-dep.js:71:10)
207 verbose stack at C:\Program Files\nodejs\node_modules\npm\node_modules\#npmcli\arborist\lib\arborist\build-ideal-tree.js:949:31
207 verbose stack at Array.map (<anonymous>)
208 verbose cwd C:\tfs\Agility\Branches\AgilityMakeover\Client\Web\AgilityItemViewer
209 verbose Windows_NT 10.0.19044
210 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install" "mocha#9.2.2"
211 verbose node v16.14.0
212 verbose npm v8.3.1
213 error Invalid Version: ^6.0.1
214 verbose exit 1
So I have no idea what this could be referring to, as far as I can tell there is no package reference. I have tried just removing the package-lock.json file and the deleting the node_modules folder and running npm install again but I keep getting this error. But I have no clue on how to progress, any advice would be appreciated
What eventually seemed to solve the problem for me was going through the list of packages shown i.e semver, can-place-dep etc and updating them all manually by doing: npm update semver and so on. I then deleted my package-lock.json and node_modules folder again and did npm install. After this I stopped getting the invalid version error. Hopefully this can help someone else if they end up having the same issue I had
Try this
Delete npm_modules folder
Delete the package.json.lock file
run npm cache clean --force
And try npm install
I'm getting an error when I create a new Vue project using vue-cli. Each time the create fails on a "Socket timeout" but a different request? I updated node using nvm and installed the latest vue-cli.
Terminal shows this:
Vue CLI v4.5.9
✨ Creating project in /Users/me/Documents/GitHub/myproject.
🗃 Initializing git repository...
⚙️ Installing CLI plugins. This might take a while...
npm ERR! code ERR_SOCKET_TIMEOUT
npm ERR! errno ERR_SOCKET_TIMEOUT
npm ERR! request to https://registry.npm.taobao.org/cosmiconfig failed, reason: Socket timeout
npm ERR! A complete log of this run can be found in:
npm ERR! /Users/me/.npm/_logs/2020-12-07T11_02_37_391Z-debug.log
ERROR command failed: npm install --loglevel error --legacy-peer-deps
The create tends to fail around the log file is around line 4900. These are the last lines in the log file:
4875 timing idealTree:node_modules/webpack-dev-server/node_modules/anymatch/node_modules/normalize-path Completed in 0ms
4876 timing idealTree:buildDeps Completed in 164233ms
4877 timing idealTree:fixDepFlags Completed in 10ms
4878 timing idealTree Completed in 164265ms
4879 timing command:install Completed in 164269ms
4880 verbose type system
4881 verbose stack FetchError: request to https://registry.npm.taobao.org/cosmiconfig failed, reason: Socket timeout
4881 verbose stack at ClientRequest.<anonymous> (/Users/me/.nvm/versions/node/v15.3.0/lib/node_modules/npm/node_modules/minipass-fetch/lib/index.js:97:14)
4881 verbose stack at ClientRequest.emit (node:events:376:20)
4881 verbose stack at TLSSocket.socketErrorListener (node:_http_client:490:9)
4881 verbose stack at TLSSocket.emit (node:events:388:22)
4881 verbose stack at emitErrorNT (node:internal/streams/destroy:188:8)
4881 verbose stack at emitErrorCloseNT (node:internal/streams/destroy:153:3)
4881 verbose stack at processTicksAndRejections (node:internal/process/task_queues:80:21)
4882 verbose cwd /Users/me/Documents/GitHub/myproject
4883 verbose Darwin 19.6.0
4884 verbose argv "/Users/me/.nvm/versions/node/v15.3.0/bin/node" "/Users/me/.nvm/versions/node/v15.3.0/bin/npm" "install" "--loglevel" "error" "--legacy-peer-deps"
4885 verbose node v15.3.0
4886 verbose npm v7.0.14
4887 error code ERR_SOCKET_TIMEOUT
4888 error errno ERR_SOCKET_TIMEOUT
4889 error request to https://registry.npm.taobao.org/cosmiconfig failed, reason: Socket timeout
4890 verbose exit 1
I ran into this as well. Fixed it by first running
vue config -e
Then setting this property to false:
{
"useTaobaoRegistry": false
}
Ok, I just updated my os to Big Sur and now it seems to work.
Updating to Big Sur did not help me.
This, however, helped:
sudo npm uninstall -g vue
sudo npm uninstall -g vue-cli
sudo npm uninstall -g #vue/cli
sudo npm cache clean --force
sudo npm install -g vue
sudo npm install -g #vue/cli
I'm stuck with an unreliable build in TeamCity.
When executing an npm install for my project that indirectly uses node-gyp to compile a solution, crucially it only fails with when executed from the TeamCity agent.
[EDIT AFTER ANSWER] The context of execution is from Build Step that executes a custom build.ps1 which automates the build process - covering c#, npm projects, executes unit tests etc. This is to say it isn't a bunch of discrete steps in TeamCity but a single PowerShell command that can execute from any environment.
If I execute from the command line on the same server, same user that the TeamCity Agent runs under, it works fine.
These are the errors from the build agent...
MSBuild: C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\MSBuild\15.0\Bin\MSBuild.exe
Executing Build
configuration: debug
Restoring npm for src\my-corp-app
> scrypt#6.0.3 preinstall D:\IR\my-corp-app\TcBuild\src\my-corp-app\node_modules\scrypt
> node node-scrypt-preinstall.js
> keccak#1.4.0 install D:\IR\my-corp-app\TcBuild\src\my-corp-app\node_modules\keccak
> npm run rebuild || echo "Keccak bindings compilation fail. Pure JS implementation will be used."
> keccak#1.4.0 rebuild D:\IR\my-corp-app\TcBuild\src\my-corp-app\node_modules\keccak
> node-gyp rebuild
D:\IR\my-corp-app\TcBuild\src\my-corp-app\node_modules\keccak>if not defined npm_config_node_gyp (node "C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin\\..\..\node_modules\node-gyp\bin\node-gyp.js" rebuild ) else (node "C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js" rebuild )
Building the projects in this solution one at a time. To enable parallel build, please add the "/m" switch.
D:\IR\my-corp-app\TcBuild\src\my-corp-app\node_modules\keccak\build\keccak.vcxproj(21,3): error MSB4019: The imported project "D:\Microsoft.Cpp.Default.props" was not found. Confirm that the path in the <Import> declaration is correct, and that the file exists on disk.
gyp ERR! build error
gyp ERR! stack Error: `msbuild` failed with exit code: 1
gyp ERR! stack at ChildProcess.onExit (C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\build.js:262:23)
gyp ERR! stack at emitTwo (events.js:126:13)
gyp ERR! stack at ChildProcess.emit (events.js:214:7)
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:198:12)
gyp ERR! System Windows_NT 10.0.14393
gyp ERR! command "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild"
gyp ERR! cwd D:\IR\my-corp-app\TcBuild\src\my-corp-app\node_modules\keccak
gyp ERR! node -v v8.12.0
gyp ERR! node-gyp -v v3.8.0
gyp ERR! not ok
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! keccak#1.4.0 rebuild: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the keccak#1.4.0 rebuild script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm WARN Local package.json exists, but node_modules missing, did you mean to install?
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\teamcity_user\AppData\Roaming\npm-cache\_logs\2019-02-13T11_38_48_872Z-debug.log
"Keccak bindings compilation fail. Pure JS implementation will be used."
The work around is to execute the command line, it succeeds, then execute in TeamCity again and the recent artifacts from the command line execution make it skip this node-gyp process and the build succeeds. This workaround is getting tiresome.
I've unsucessfully followed the various googled suggestions for fixing "C:\Microsoft.Cpp.Default.props" was not found errors:
npm install --global --production windows-build-tools
Set / Clear VCTargetsPath
Have also compared the environment variables between my CLI prompt and TeamCity Agent when executing the build but the only differences are the expected additions for TeamCity JRE and build numbers.
Am currently stuck trying to determine what magic makes the install work from an interactive CLI as opposed to TeamCity agent running as a Windows Service
The complete log referred to in the above log has details like
0 info it worked if it ends with ok
1 verbose cli [ 'C:\\Program Files\\nodejs\\node.exe',
1 verbose cli 'C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli 'run',
1 verbose cli 'rebuild' ]
2 info using npm#6.4.1
3 info using node#v8.12.0
4 verbose run-script [ 'prerebuild', 'rebuild', 'postrebuild' ]
5 info lifecycle keccak#1.4.0~prerebuild: keccak#1.4.0
6 info lifecycle keccak#1.4.0~rebuild: keccak#1.4.0
7 verbose lifecycle keccak#1.4.0~rebuild: unsafe-perm in lifecycle true
8 verbose lifecycle keccak#1.4.0~rebuild: PATH: C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;D:\IR\my-corp-app\TcBuild\src\my-corp-app-node\node_modules\keccak\node_modules\.bin;D:\IR\my-corp-app\TcBuild\src\my-corp-app-node\node_modules\.bin;C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;D:\IR\my-corp-app\TcBuild\src\my-corp-app-node\node_modules\keccak\node_modules\.bin;D:\IR\my-corp-app\TcBuild\src\my-corp-app-node\node_modules\.bin;C:\Windows\Microsoft.NET\Framework64\v4.0.30319\;C:\ProgramData\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\Amazon\cfn-bootstrap\;C:\ProgramData\chocolatey\bin;C:\Program Files\Microsoft SQL Server\Client SDK\ODBC\130\Tools\Binn\;C:\Program Files (x86)\Microsoft SQL Server\140\Tools\Binn\;C:\Program Files\Microsoft SQL Server\140\Tools\Binn\;C:\Program Files\Microsoft SQL Server\140\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\Client SDK\ODBC\130\Tools\Binn\;C:\Program Files (x86)\Microsoft SQL Server\140\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\140\Tools\Binn\ManagementStudio\;C:\Program Files\dotnet\;C:\Program Files\Microsoft\Web Platform Installer\;C:\Program Files\Microsoft SQL Server\130\Tools\Binn\;C:\Program Files (x86)\Microsoft SQL Server\110\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\120\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\130\DTS\Binn\;D:\apps\jdbc;C:\Program Files\Git\cmd;D:\apps\OpenSSL-Win64\bin;C:\Program Files\nodejs\;C:\Users\teamcity_user\AppData\Local\Microsoft\WindowsApps;C:\Users\teamcity_user\AppData\Roaming\npm;C:\Users\teamcity_user\.dotnet\tools
9 verbose lifecycle keccak#1.4.0~rebuild: CWD: D:\IR\my-corp-app\TcBuild\src\my-corp-app-node\node_modules\keccak
10 silly lifecycle keccak#1.4.0~rebuild: Args: [ '/d /s /c', 'node-gyp rebuild' ]
11 silly lifecycle keccak#1.4.0~rebuild: Returned: code: 1 signal: null
12 info lifecycle keccak#1.4.0~rebuild: Failed to exec rebuild script
13 verbose stack Error: keccak#1.4.0 rebuild: `node-gyp rebuild`
13 verbose stack Exit status 1
13 verbose stack at EventEmitter.<anonymous> (C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\index.js:301:16)
13 verbose stack at emitTwo (events.js:126:13)
13 verbose stack at EventEmitter.emit (events.js:214:7)
13 verbose stack at ChildProcess.<anonymous> (C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14)
13 verbose stack at emitTwo (events.js:126:13)
13 verbose stack at ChildProcess.emit (events.js:214:7)
13 verbose stack at maybeClose (internal/child_process.js:915:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)
14 verbose pkgid keccak#1.4.0
15 verbose cwd D:\IR\my-corp-app\TcBuild\src\my-corp-app-node\node_modules\keccak
16 verbose Windows_NT 10.0.14393
17 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "run" "rebuild"
18 verbose node v8.12.0
19 verbose npm v6.4.1
20 error code ELIFECYCLE
21 error errno 1
22 error keccak#1.4.0 rebuild: `node-gyp rebuild`
22 error Exit status 1
23 error Failed at the keccak#1.4.0 rebuild script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]
Finally solved this by adding an inserting extra (and redundant) PowerShell build step:
Runner Type: PowerShell
Script: SourceCode
Working directory: <the obvious folder>
Script Source: npm install
and it magically worked.
Now, of course I already was executing npm install from deep down inside my build automation build.ps1.
For some reason, the above works and the buried one doesn't. I can't explain why. Confirmed that the execution folder was correct and also used get-command npm from both contexts and the result was the same for both:
CommandType Name Version Source
----------- ---- ------- ------
Application npm.cmd 0.0.0.0 C:\Program Files\nodejs\npm.cmd
Getting this every time I try to install mean.io application have tried
npm cache clean,
tried total reinstall ,
going mad at the moment . Am also running this as administrator. pleas help
C:\Users\mmcelhinney\pitch_v1>npm install
-
> phantomjs#1.9.18 install C:\Users\mmcelhinney\pitch_v1\node_modules\phantomjs
> node install.js
Download already available at C:\Users\MMCELH~1\AppData\Local\Temp\phantomjs\phantomjs-1.9.8-windows.zip
Extracting zip contents
Removing C:\Users\mmcelhinney\pitch_v1\node_modules\phantomjs\lib\phantom
Copying extracted folder C:\Users\MMCELH~1\AppData\Local\Temp\phantomjs\phantomjs-1.9.8-windows.zip-extract-1456238458670\phantomjs-1.9.8-windows -> C:\Users\mmcelhinney\pitch_v1\node_modules\phantom
s\lib\phantom
Phantom installation failed { [Error: EPERM, unlink 'C:\Users\MMCELH~1\AppData\Local\Temp\phantomjs\phantomjs-1.9.8-windows.zip-extract-1456238458670\phantomjs-1.9.8-windows\phantomjs.exe']
errno: -4048,
code: 'EPERM',
path: 'C:\\Users\\MMCELH~1\\AppData\\Local\\Temp\\phantomjs\\phantomjs-1.9.8-windows.zip-extract-1456238458670\\phantomjs-1.9.8-windows\\phantomjs.exe' } Error: EPERM, unlink 'C:\Users\MMCELH~1\App
ata\Local\Temp\phantomjs\phantomjs-1.9.8-windows.zip-extract-1456238458670\phantomjs-1.9.8-windows\phantomjs.exe'
at Error (native)
npm ERR! Windows_NT 6.1.7601
npm ERR! argv "C:\\Program Files\\nodejs\\\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install"
npm ERR! node v0.12.0
npm ERR! npm v2.5.1
npm ERR! code ELIFECYCLE
npm ERR! phantomjs#1.9.18 install: `node install.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the phantomjs#1.9.18 install script 'node install.js'.
npm ERR! This is most likely a problem with the phantomjs package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node install.js
npm ERR! You can get their info via:
npm ERR! npm owner ls phantomjs
npm ERR! There is likely additional logging output above.
npm ERR! error rolling back Error: EPERM, unlink 'C:\Users\mmcelhinney\pitch_v1\node_modules\phantomjs\lib\phantom\phantomjs.exe'
npm ERR! error rolling back at Error (native)
npm ERR! error rolling back { [Error: EPERM, unlink 'C:\Users\mmcelhinney\pitch_v1\node_modules\phantomjs\lib\phantom\phantomjs.exe']
npm ERR! error rolling back errno: -4048,
npm ERR! error rolling back code: 'EPERM',
npm ERR! error rolling back path: 'C:\\Users\\mmcelhinney\\pitch_v1\\node_modules\\phantomjs\\lib\\phantom\\phantomjs.exe' }
Excerpt from Debug log as well :
6379 info phantomjs#1.9.18 Failed to exec install script
6380 verbose unlock done using C:\Users\mmcelhinney\AppData\Roaming\npm-cache_locks\phantomjs-69c2bf63828d859c.lock for C:\Users\mmcelhinney\pitch_v1\node_modules\phantomjs
6381 verbose stack Error: phantomjs#1.9.18 install: node install.js
6381 verbose stack Exit status 1
6381 verbose stack at EventEmitter. (C:\Program Files\nodejs\node_modules\npm\lib\utils\lifecycle.js:213:16)
6381 verbose stack at EventEmitter.emit (events.js:110:17)
6381 verbose stack at ChildProcess. (C:\Program Files\nodejs\node_modules\npm\lib\utils\spawn.js:14:12)
6381 verbose stack at ChildProcess.emit (events.js:110:17)
6381 verbose stack at maybeClose (child_process.js:1008:16)
6381 verbose stack at Process.ChildProcess._handle.onexit (child_process.js:1080:5)
Try my solution here https://stackoverflow.com/a/35043377/5734480
It may be slightly different depending on your OS.
After installation, the new jhipster project appeared here such error:
it is log file npm-debug.log:
1891 verbose stack at Request.emit (events.js:185:7)
1891 verbose stack at Request.<anonymous> (C:\Program Files\nodejs\node_modules\npm\node_modules\request\request.js:1082:10)
1891 verbose stack at emitOne (events.js:95:20)
1891 verbose stack at Request.emit (events.js:182:7)
1891 verbose stack at IncomingMessage.<anonymous> (C:\Program Files\nodejs\node_modules\npm\node_modules\request\request.js:1009:12)
1892 verbose cwd D:\projects\jproject
1893 error Windows_NT 6.1.7601
1894 error argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install"
1895 error node v5.5.0
1896 error npm v3.3.12
1897 error Unexpected end of input
1897 error {"_id":"karma","_rev":"632-143ecb8b5235e3c97cf3d4b359599b72","name":"karma","description":"Spectacular Test Runner for JavaScript.","dist-tags":{"latest":"0.13.19"},"versions":{"0.8.0":{"name":"karma","description":"Spectacular Test Runner for JavaScript.","homepage":"http://karma-runner.github.com/","bugs":{"url":"https://github.com/karma-runner/karma/issues"},"keywords":["karma","spectacular","runner","testacular","js","javascript","testing","test","...
.8.4"},"peerDependencies":{"karma-jasmine":"*","karma-requirejs":"*","karma-coffee-preprocessor":"*","karma-html2js-preprocessor":"*","karma-chrome-launcher":"*","karma-firefox-launcher":"*","karma-phantomjs-launcher":"*","karma-script-launcher":"*"},"devDependencies":{"grunt":"~0.4","grunt-simple-mocha":"git://github.com/yaymukund/grunt-simple-mocha.git","grunt-contrib-jshint":"~0.3","grunt-coffeelint":"~0.0.6","grunt-npm":"~0.0.1","grunt-bump":"~0.0.
1898 error If you need help, you may report this error at:
1898 error <https://github.com/npm/npm/issues>
1899 verbose exit [ 1, true ]
Help me why this error occurs?
As written in the documentation, you must install Grunt before installing JHipster.
If you don't know how to do this, we also provide a Vagrant box where it's already installed.