Geek Answers Handbook

Server sometimes returns 500 when installing angular2

Recently, I have experienced that installing jspm most often does not cause the server to return status 500 whenever @ angular packages are downloaded via NPM. I tried everything:

  • Npm authentication
  • try new registries
  • checked the npm status page

However, none of them can give me clues why angular packages sometimes fail, sometimes this one, next time it's different ... but always @angular packages ... maybe they are hosted on a google server that behaves strangely ? Everything seems to be fine until June 9th ...

JSPM does not seem to have verbose mode, so its an assumption if the server provided additional information on why it is not working ...

Also, I’m not sure if this is the right forum for this, as it is an infrastructure for programming and not really programming issues ...

Yours faithfully

+4
source share
2 answers

Well, as mentioned in the jakeniemiec-related issue, it’s obvious that "npm makes changes to its API and breaks the API, that the npm CLI tool is not directly dependent on it, but what are we doing."

Although this answer is probably not a big deal for our children and grandchildren, I want to report that this particular case was due to this.

, , , - , , .

0

, ; :

, , npm, npm login. jspm install. jspm cli, , npmjs.

npm, 500 . , , .

+1

More articles:


All Articles