jspm-cli: Keep getting status code 500 when using scoped npm packages

Hi,

I tried to install some new dependencies today. When I try to run jspm install, I get errors like this:

err  Error on lookup for npm:@angular/core
Invalid status code 500

err  Error on lookup for npm:@angular/platform-browser-dynamic
Invalid status code 500

err  Error on lookup for npm:@ngrx/store
Invalid status code 500

err  Error looking up npm:@angular/core.

or this:

err  Error: socket hang up
    at createHangUpError (_http_client.js:250:15)
    at TLSSocket.socketOnEnd (_http_client.js:342:23)
    at emitNone (events.js:91:20)
    at TLSSocket.emit (events.js:185:7)
    at endReadableNT (_stream_readable.js:926:12)
    at _combinedTickCallback (internal/process/next_tick.js:74:11)
    at process._tickCallback (internal/process/next_tick.js:98:9)

err  Error on lookup for npm:@angular/compiler
Invalid status code 500

err  Error on lookup for npm:@angular/core
Invalid status code 500

err  Error on lookup for npm:@angular/platform-browser
Invalid status code 500

err  Error on lookup for npm:@ngrx/core
Invalid status code 500

err  Error looking up npm:@angular/compiler.

The number of erroring requests seems to vary and when I try to install one of those package at a time, it seems to work sometimes and sometimes it does not (tested with npm:@angular/core).

I tried update my JSPM (from v0.17.0.beta.14 to v0.17.0-beta.21), but got the same problem. A colleague had the same problem when I asked him to reproduce the issue. It works without problems when installing the problematic packages via npm.

I reproduced the behaviour in this project: https://github.com/flaviait/ng2-jspm-template

Any ideas what could be causing this issue?

About this issue

Original URL
State: closed
Created 8 years ago
Reactions: 16
Comments: 18 (10 by maintainers)

Most upvoted comments

@guybedford @screendriver I am in contact with npm support on this. I’ll update here if I find anything out.

jakeNiemiec on Jun 15, 2016

Everything seems to work more often if you are logged in to npm login

I am always logged in to npm and had the issue yesterday as well. But now it seems to work at the moment.

I’m curious about the cause of this issue. Our whole continuous integration system went down yesterday because of this.

screendriver on Jun 14, 2016

See: https://gitter.im/jspm/jspm?at=575f22466092456f6633da6c

1000 curl requests to https://registry.npmjs.org/angular returns:

1000 http_status: 200

1000 curl requests to https://registry.npmjs.org/@angular%2Fupgrade returns:

730 http_status: 401
248 http_status: 500
22 http_status: 200
Total = 1000

This is reasonable proof that this is an npm hosting problem.

jakeNiemiec on Jun 13, 2016

Indeed, noticed the same here and tried about everything in my power:

Authenticating
Clearing caches (one becomes paranoia)
Extending timeouts (although the chances for this work were dismal as jspm is normally able to detect this…)

Is there a possibility that angular2 is hosting their own npm service and that this seems to fail for whatever reason?

I have also created an SO question on the topic (which actually guided me here): http://stackoverflow.com/questions/37790812/server-sometimes-returns-500-when-installing-angular

Maybe here I can cast my vote for a verbose mode, in which we can learn if besides the 500 code, we can actually see some output that the server might have send additionally (e.g. server flooded, google out-of-money, … ) ?

UXabre on Jun 13, 2016

Seems like the problem resolved itself now? At least in my case I can use jspm install again as expected 😃

UXabre on Jun 14, 2016