NPM Error Parsing Json, Unexpected Token

Question

I'm trying to install grunt, but no luck.

npm install -g grunt-cli --registry http://registry.npmjs.org/

gives this error:

npm ERR! registry error parsing json
npm ERR! Darwin 14.3.0
npm ERR! argv "node" "/usr/local/bin/npm" "install" "-g" "grunt-cli" "--registry" "http://registry.npmjs.org/"
npm ERR! node v0.12.4
npm ERR! npm  v2.10.1
npm ERR! Unexpected token <
npm ERR! <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
npm ERR! <html><head>
npm ERR! <title>404 Not Found</title>
npm ERR! </head><body>
npm ERR! <h1>Not Found</h1>
npm ERR! <p>The requested URL /grunt-cli was not found on this server.</p>
npm ERR! </body></html>

What could be wrong?

Any reason you're trying to specify the registry? Did you try just npm install -g grunt-cli? From the body, it looks like it can't find grunt-cli on that server. — Brennan
– Brennan, Commented Jun 12, 2015 at 19:26
@Brennan I did try that. it gives me this error "Error: connect ECONNREFUSED" — Jaeeun lee
– Jaeeun lee, Commented Jun 12, 2015 at 19:54
That's odd. I just did it and it works for me. Do you have an .npmrc or something that would change your default registry? You may also try using --registry https://registry.npmjs.org/ (note the https). — Brennan
– Brennan, Commented Jun 12, 2015 at 19:56
@Brennan I'm sorry, but I'm actually not sure what .npmrc is. Could that be the problem? Tried https, gave me this error "tunneling socket could not be established, cause=connect ECONNREFUSED" "in most cases you are behind a proxy or have bad network settings." — Jaeeun lee
– Jaeeun lee, Commented Jun 12, 2015 at 20:39
An .npmrc is a file that you can set defaults for the npm tool to use. It doesn't look like that's the issue. Are you behind some firewall or proxy as the message suggests? — Brennan
– Brennan, Commented Jun 12, 2015 at 20:46

Community · Accepted Answer · 2020-06-20 09:12:55Z

29

I just ran the command,

first:

$ rm -f package-lock.json

after:

$ npm i

work for me ;)

edited Jun 20, 2020 at 9:12

CommunityBot

11 silver badge

answered Jul 24, 2017 at 16:35

rflmyk

5696 silver badges13 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

Adam Harte Over a year ago

Yup, just deleted the package-lock.json file and everything starting working again.

Jaeeun lee · Accepted Answer · 2015-06-12 20:57:43Z

22

This did it for me, although not sure why.

npm config rm proxy
npm config rm https-proxy

http://jonathanblog2000.blogspot.ch/2013/11/set-and-reset-proxy-for-git-and-npm.html

answered Jun 12, 2015 at 20:57

Jaeeun lee

4561 gold badge3 silver badges11 bronze badges

1 Comment

Rafael Over a year ago

@TylerChong rm -f package-lock.json && npm install

Collectives™ on Stack Overflow

NPM Error Parsing Json, Unexpected Token

2 Answers 2

first:

after:

1 Comment

1 Comment

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

first:

after:

1 Comment

1 Comment

Your Answer

Sign up or log in

Post as a guest

Linked

Related