Unable to publish package - npm ERR! registry error parsing json

[cstro]

I'm trying to publish a private package and I keep getting the following error:

npm ERR! registry error parsing json
npm ERR! registry error parsing json
npm ERR! registry error parsing json
npm ERR! publish Failed PUT 500
npm ERR! Unexpected token A in JSON at position 0
npm ERR! An error occurred

Have also experienced the same issue on a different machine and with a different user account.

• NPM version: 6.2.0
• Node version: v8.9.3

[winterbe]

Same problem here:

npm info attempt registry request try #1 at 16:48:36
npm http request PUT https://registry.npmjs.org/sequency
npm http 500 https://registry.npmjs.org/sequency
npm ERR! registry error parsing json
npm info retry will retry, error on last attempt: SyntaxError: Unexpected token A in JSON at position 0
npm info retry An error occurred
npm info attempt registry request try #2 at 16:48:48
npm http request PUT https://registry.npmjs.org/sequency
npm http 500 https://registry.npmjs.org/sequency
npm ERR! registry error parsing json
npm info retry will retry, error on last attempt: SyntaxError: Unexpected token A in JSON at position 0
npm info retry An error occurred
npm info attempt registry request try #3 at 16:49:49
npm http request PUT https://registry.npmjs.org/sequency
npm http 500 https://registry.npmjs.org/sequency
npm ERR! registry error parsing json
npm ERR! publish Failed PUT 500
npm ERR! Unexpected token A in JSON at position 0
npm ERR! An error occurred
npm timing npm Completed in 100645ms

Node version v8.11.1
NPM version 6.2.0

[Kalmhh]

I have the exact same problem, trying to publish a private package having :

npm ERR! registry error parsing json
npm ERR! registry error parsing json
npm ERR! registry error parsing json
npm ERR! publish Failed PUT 500
npm ERR! Unexpected token A in JSON at position 0
npm ERR! An error occurred

Node version 9.8.0
NPM version 6.2.0

[cstro]

Looks like it's being investigated now https://status.npmjs.org/

[dougwilson]

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.

[Kalmhh]

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

[cstro]

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.

[winterbe]

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> .

[Kalmhh]

The Error is back..

[sentinel09]

I receive 500 error again while publishing.