npm Community Forum (Archive)

The npm community forum has been discontinued.

To discuss usage of npm, visit the GitHub Support Community.

Unable to find a readme for @azure/app-configuration@1.0.0-preview.1

What I Wanted to Do

Have the npm website show the in the package at

What Happened Instead

The npm website shows “Unable to find a readme for @azure/app-configuration@1.0.0-preview.1”


The package appears to contain a valid readme:

Another package was published shortly prior to @azure/app-configuration, and the npm website is showing the readme correctly:

When we published this package again (as preview.2), the readme is shown correctly:

Platform Info

$ npm --versions
{ npm: '6.9.0',            
  ares: '1.15.0',          
  brotli: '1.0.7',         
  cldr: '35.1',            
  http_parser: '2.8.0',    
  icu: '64.2',             
  modules: '64',           
  napi: '4',               
  nghttp2: '1.34.0',       
  node: '10.16.1',         
  openssl: '1.1.1c',       
  tz: '2019a',             
  unicode: '12.1',         
  uv: '1.28.0',            
  v8: '',
  zlib: '1.2.11' }         

$ node -p process.platform

There was a similar report recently, but no solution: README not published for @solid/react

This looks like a transient failure in the npm website

I just ran in to this when publishing a package( the is in the tarball but the site side says “Unable to find a readme for @senzing/sdk-components-ng@1.0.9”

so, is this an intermittent issue that will correct itself? or does this require manual intervention. it would be absolutely awful if I need to bump up the version number just to get the readme in there.

I really wish npm would come up with a better way to handle version unpublish… cause y’know, sometimes *hit happens.