-
Notifications
You must be signed in to change notification settings - Fork 47
Unable to publish package - npm ERR! registry error parsing json #377
Comments
Same problem here:
Node version |
I have the exact same problem, trying to publish a private package having : npm ERR! registry error parsing json Node version |
Looks like it's being investigated now https://status.npmjs.org/ |
When I tried (before seeing it was down), I even got the successful publish email, through of course it doesn't seem like it was successful. I hope that did not put the module into some kind of weird limbo with that version number. |
Just received a mail of publishing confirmation, but never seen the npm publish pass the 'registry error parsing json' ERR ... |
Status page says "Monitoring - Packages are now publishing successfully. We are continuing to monitor the registry." I've managed to successfully publish my package now, however when I was publishing it still throws the error, just without the 500. Edit: It's also gives me zero indication that it did publish successfully, it even re-asks me to re-enter my OTP. |
Same here. Just received a confirmation email that the package has been
published although I got described error via cli.
Kalmhh <notifications@github.com> schrieb am Mo. 30. Juli 2018 um 17:50:
… Just received a mail of publishing confirmation, but never seen the npm
publish pass the 'registry error parsing json' ERR ...
So I don't even know if it is really published, and well published
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<https://github.com/npm/registry/issues/377#issuecomment-408912546>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAdmqW7C2_q8PZaTu4X_86zmLimn-bidks5uLytigaJpZM4VmkAC>
.
|
The Error is back.. |
I receive 500 error again while publishing. |
I'm trying to publish a private package and I keep getting the following error:
Have also experienced the same issue on a different machine and with a different user account.
6.2.0
v8.9.3
The text was updated successfully, but these errors were encountered: