According to this NPM status dashboard <http://status.npmjs.org/incidents/nl2mpgltpnvj>, this was an issue with tarball serving which should have been resolved as of Jul 06, 2016 - 17:01 UTC. The status report states there will be a post about it on the NPM blog <http://blog.npmjs.org/> but none exists thus far. The related NPM github issue 13284 <https://github.com/npm/npm/issues/13284> has been closed for 2 hours.
In short, this appears to have been resolved according to the NPM team's posts. Are you still reliably experiencing this error when attempting to deploy your application? On Wednesday, July 6, 2016 at 6:28:18 AM UTC-4, Aurélien C wrote: > > Hi > > This morning I keep getting npm issues when trying to deploy my nodejs app > in GAE > > Example log before it fails: > npm ERR! fetch failed > https://registry.npmjs.org/babel-plugin-transform-react-constant-elements/-/babel-plugin-transform-react-constant-elements-6.9.1.tgz > npm WARN retry will retry, error on last attempt: Error: fetch failed with > status code 502 > npm ERR! fetch failed > https://registry.npmjs.org/algoliasearch/-/algoliasearch-3.16.0.tgz > npm WARN retry will retry, error on last attempt: Error: fetch failed with > status code 502 > > Any ideas? > > (I did a fresh `npm install` locally and it works) > > Thanks! > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/0f6d07e6-545c-4672-8b61-76ceda661b7a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
