Same here: 

ERR! registry error parsing json
...

npm ERR! TypeError: Property 'onIncoming' of object #<HTTPParser> is not a 
function
npm ERR!     at HTTPParser.parserOnHeadersComplete (_http_common.js:110:23)
npm ERR!     at TLSSocket.socketOnData (_http_client.js:272:20)
npm ERR!     at TLSSocket.EventEmitter.emit (events.js:103:17)
npm ERR!     at readableAddChunk (_stream_readable.js:156:16)
npm ERR!     at TLSSocket.Readable.push (_stream_readable.js:123:10)
npm ERR!     at TCP.onread (net.js:508:20)
npm ERR! If you need help, you may report this log at:
npm ERR!     <http://github.com/isaacs/npm/issues>
npm ERR! or email it to:
npm ERR!     <[email protected]>

Trying to install bower.

On Monday, 4 November 2013 20:10:12 UTC, suprUtah wrote:
>
> also get a  "fetch failed" followed by "network socket hangup"
>
> On Monday, November 4, 2013 11:25:40 AM UTC-6, Chris Scribner wrote:
>>
>> I'm getting a lot of "error parsing json" errors when trying to install 
>> npm today.
>>
>> $ npm install lru-cache
>> npm http GET https://registry.npmjs.org/lru-cache/2.3.0
>> npm http 500 https://registry.npmjs.org/lru-cache/2.3.0
>> npm ERR! registry error parsing json
>>
>> memwatch and several other projects also seem to have the same problem.
>>
>> This is occurring locally, but also from a build server in a different 
>> state.
>>
>

-- 
-- 
Job Board: http://jobs.nodejs.org/
Posting guidelines: 
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"nodejs" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to