-
Notifications
You must be signed in to change notification settings - Fork 48
Readmes missing after yesterday's registry outage #418
Comments
Same here they will appear but after some time... |
We published these packages 24h ago, so "some time" already passed :D. In general, it seems that there's a lot of mess after yesterday (see e.g. https://github.com/npm/registry/issues/327#issuecomment-391339350). |
I have the same problem when publishing a package. There exist a README.md but I get the message |
Still missing ;/ It'd be nice to at least get an information that we should publish new versions of these packages because npm will not resolve this issue automatically. cc @jefflembeck |
Turns out that this wasn't an issue with the registry. Today I released the same set of packages and different ones don't have readmes: #442. I'm closing this ticket as it can be misleading that this issue was caused by the outage. |
Link to the page
E.g.:
More info
This issue started yesterday together with yesterday's registry issues (https://github.com/npm/registry/issues/324). However, it does not happen for all packages published at that moment. E.g. https://www.npmjs.com/package/@ckeditor/ckeditor5-link is fine (all 3 mentioned packages were released together).
The text was updated successfully, but these errors were encountered: