Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Package readme content is missing #72

Open
lini opened this issue Jan 10, 2018 · 3 comments
Open

Package readme content is missing #72

lini opened this issue Jan 10, 2018 · 3 comments

Comments

@lini
Copy link

lini commented Jan 10, 2018

Take for example the following package, which has readme content on the npmjs page:
https://www.npmjs.com/package/nativescript-floatingactionbutton

The readme content, however, is not in the registry:
http://registry.npmjs.org/nativescript-floatingactionbutton

and therefore no readme in the npms info as well:
https://api.npms.io/v2/package/nativescript-floatingactionbutton

Is there a way for npms to retrieve the readme in some other?

For comparison, a package that has readme everywhere:
https://www.npmjs.com/package/nativescript-push-notifications
http://registry.npmjs.org/nativescript-push-notifications
https://api.npms.io/v2/package/nativescript-push-notifications

@abishekrsrikaanth
Copy link

same applies for vue project as well, but I do see the content for it on https://www.npmjs.com/package/vue

@satazor
Copy link
Member

satazor commented Nov 6, 2018

It seems that https://www.npmjs.com/package/nativescript-floatingactionbutton has no readme in the npm info page.

What we could do is attempt to fallback to the repo README if there's one. That's actually easy to do because we download the package.

@JoshuaAYoung
Copy link

Hi there! I am part of a team of Thinkful bootcamp students that are using your wonderful package to create our final capstone project, npmm. We are using react-markdown to display npm readmes but are also running into this issue with many of them missing. Including some important packages like react, which surprised us. I'm assuming that was a conscious decision by react not to include a readme on the npm page. Weird though.

Anyway, just wondering if a fix for this was still in the works.

Thanks for the awesome API!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants