README.md not displayed in recently-published scoped packages about www HOT 9 CLOSED

@ashleygwilliams We're directing people to these package pages and it makes us look super-broken. Is there any workaround?

from www.

@RyanCavanaugh The couch package document appears to point at the correct README.md filename (via readmeFilename), however the "readme" key in the couch package document points at an empty string. That key is populated by the CLI on publish, and used by the website to display readme data — when it's missing we display the above error. I'm looking through the readme processing logs now and I don't see any errors importing the package document, which leads me to suspect that the data wasn't added by the CLI during publish. Are you using npm publish to publish this package?

from www.

@chrisdickinson No, we've switched to using the API. Code here https://github.com/Microsoft/types-publisher/blob/master/src/lib/npm-client.ts#L1

/cc @andy-ms

from www.

So it sounds like we need to read the README.md contents and put it into the readme key during our API-based publish? It's super surprising to me that these things work differently but it sounds like an easy fix on our end.

from www.

Closing. Thanks for answering, @chrisdickinson !

from www.

@RyanCavanaugh Yep! Apologies for the surprise. Our goal is to start providing documentation for the existing registry API on the registry repo, but it's a work in progress!

from www.

Hi, it's us again!

Some packages are not showing the latest data available. For example, d3 says that "0.0.33 is the latest of 15 releases", but actually 3.5.34 was published yesterday and is the latest of 16 releases. (Also, the readme contents are old.)

Here's the background: we are directly using the publish method from npm-registry-client.
Currently we use a very simple technique to get the metadata: we read in the contents of README.md and attach it to the package.json.

I suspect that we are still not providing all of the metadata needed. Is there something else we need to be doing there?

(The new issue is microsoft/types-publisher#140.)

from www.

@andy-ms can you log a new issue? Seems this isn't getting any visibility

from www.

@RyanCavanaugh #34

from www.