search

npm / www

community space for the npm website
https://npm.community
69 stars 48 forks source link

Readmes missing after yesterday's registry outage #418

Closed Reinmar closed 6 years ago

Reinmar commented 6 years ago

Link to the page

E.g.:

screen shot 2018-05-23 at 10 26 21

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).

pjasiun commented 6 years ago

Same here: https://www.npmjs.com/package/@ckeditor/letters

Stradivario commented 6 years ago

Same here they will appear but after some time...

Reinmar commented 6 years ago

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).

liudonghua123 commented 6 years ago

I have the same problem when publishing a package. There exist a README.md but I get the message "Unable to find a readme for glade-ui-parse-cli@1.0.0" My published package is on https://www.npmjs.com/package/glade-ui-parse-cli

Reinmar commented 6 years ago

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

Reinmar commented 6 years ago

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: https://github.com/npm/www/issues/442.

I'm closing this ticket as it can be misleading that this issue was caused by the outage.