<p dir="auto"><a target="_blank" rel="noopener noreferrer nofollow" href="https://user-images.githubusercontent.com/53021413/71420997-346aa200-2689-11ea-838e-81ae22bf54ea.JPG"><img src="https://user-images.githubusercontent.com/53021413/71420997-346aa200-2689-11ea-838e-81ae22bf54ea.JPG" alt="123" style="max-width: 100%;"></a><br>
I would appreciate if you make a comeback here.</p>
<p dir="auto">The <a href="https://www.npmjs.com/package/@types/ssri" rel="nofollow">npm page for @types/ssri</a>, for example, incorrectly claims there is no README, even though when you install that package, there is a README. This is happening for all packages published by the Definitely Typed publisher to the <code class="notranslate">@types/</code> scope since June 20.</p>
<p dir="auto">Since Definitely Typed publishes a lot of packages, I was able to narrow the break down to the span between @types/react-vis@1.11.1:"2020-06-19T06:34:23.672Z" and @types/ssri@7.1.0: "2020-06-20T19:36:22.490Z". Somewhere between the 19th and 20th packages stopped showing their READMEs.</p>
<p dir="auto">No code changes to our publisher happened in that time span, nor did a new version of the npm package get published.<br>
And the couch packages are very similar:</p>
<ul dir="auto">
<li><a href="http://registry.npmjs.org/@types/react-vis" rel="nofollow">http://registry.npmjs.org/@types/react-vis</a> (good)</li>
<li><a href="http://registry.npmjs.org/@types/ssri" rel="nofollow">http://registry.npmjs.org/@types/ssri</a> (bad)</li>
</ul>
<p dir="auto">Both jsons have a "readme" key with the readme contents, and a readmeFilename key that is just the empty string. When installed, both packages have near-identical READMEs. Even the order of the couch package keys is the same.</p>
<h3 dir="auto">Steps to Reproduce</h3>
<p dir="auto">Recreate the package structure published by <a href="https://github.com/microsoft/DefinitelyTyped-tools">https://github.com/microsoft/DefinitelyTyped-tools</a>: generate-packages.ts and package-publisher.ts are the interesting files. Let me know if this is needed and I can try to create a standalone repro. However, I'm mostly interested in having npm insiders</p>
<ol dir="auto">
<li>Look at the good-vs-bad couch packages for differences.</li>
<li>Check whether npm changed something related to README somewhere between June 19 and 20.</li>
</ol>
<h3 dir="auto">Expected Behavior</h3>
<p dir="auto">README should be visible on the npmjs.com page.</p>
<h2 dir="auto">References</h2>
<ul dir="auto">
<li>Could be a duplicate of <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="609241866" data-permission-text="Title is private" data-url="https://github.com/npm/cli/issues/1221" data-hovercard-type="issue" data-hovercard-url="/npm/cli/issues/1221/hovercard" href="https://github.com/npm/cli/issues/1221">#1221</a>, except that it didn't start until much later, and we use the npm package to publish rather than the CLI.</li>
</ul>