Incorrect README displayed when GitHub repository linked as homepage about www HOT 5 CLOSED

Yeah, or the CLI team, so that the new README gets packaged up at publish time by read-package-json

from www.

@ashleygwilliams Do you have an ETA on when this will be fixed? Thanks!

from www.

This is a bit tricky: it's not a website bug, since we just display what the registry API gives us.

The registry stores a copy of the README separate from your package contents, and that's what we display. That may vary by npm CLI tool version, when it reads and embeds that data into the package metadata at publish time. Did you change versions of the CLI in use at the time?

For support on an individual basis (rather than bug reporting), you can contact [email protected] and the support team can work to make sure your specific case is taken care of. A broader change will require understanding the bug and use-case and integrating a fix into the appropriate place -- the registry team's issue tracker and CLI team's

from www.

@aredridel Thanks for looking into this. There appears to be no way to explicitly assign a README in package.json, so if I wanted something like that, I'm guessing I'd have to file an issue with the registry team?

from www.

I filed an issue here.

from www.