Requests for the latest 1.x release are now failing: https://unpkg.com/[email protected]/
Seems like some weird issue with the registry itself. Any chance you can publish 1.1.4 as a temporary workaround?
erquhart
👍7
All 6 comments
I'm experiencing the same issue, but have noticed that 1.1.3 appears to be available in npm?
$ npm show chalk@* version
npm info it worked if it ends with ok
npm info using [email protected]
npm info using [email protected]
npm info attempt registry request try #1 at 7:39:15 PM
npm http request GET https://registry.npmjs.org/chalk
npm http 200 https://registry.npmjs.org/chalk
[email protected] '0.1.0'
[email protected] '0.1.1'
[email protected] '0.2.0'
[email protected] '0.2.1'
[email protected] '0.3.0'
[email protected] '0.4.0'
[email protected] '0.5.0'
[email protected] '0.5.1'
[email protected] '1.0.0'
[email protected] '1.1.0'
[email protected] '1.1.1'
[email protected] '1.1.2'
[email protected] '1.1.3'
[email protected] '2.0.0'
[email protected] '2.0.1'
[email protected] '2.1.0'
[email protected] '2.2.0'
[email protected] '2.2.2'
[email protected] '2.3.0'
npm info ok
arwineap
on 8 Nov 2017
I can curl the endpoint now, appears resolved?
recurrence
on 8 Nov 2017
👍1
@recurrence I can do so too, but trying to install through npm -i always results in a 503 for me.
GrimTheReaper
on 8 Nov 2017
I think the inconsistencies are due to various caches.
erquhart
on 8 Nov 2017
It was tracked down to cloudflare, cloudflare claims the outage has ended: https://github.com/yarnpkg/yarn/issues/4889#issuecomment-342936836
recurrence
on 8 Nov 2017
Ah yep, Travis has it now, awesome. Thanks for the link!
erquhart
on 8 Nov 2017
🎉2
Was this page helpful?
0 / 5 - 0 ratings
Related issues
macOneOone
路
6Comments
sindresorhus
路
4Comments
Elberet
路
4Comments
ORESoftware
路
6Comments
ExE-Boss
路
4Comments
Most helpful comment
Ah yep, Travis has it now, awesome. Thanks for the link!