At https://www.npmjs.com/package/estraverse, it says there is no readme:
This is because the published package does not include README.md:
$ tar tvf $(npm pack estraverse)
-rw-rw-rw- 0 0 0 1016 Mar 10 2016 package/package.json
-rw-rw-rw- 0 0 0 27642 Mar 10 2016 package/estraverse.js
-rw-rw-rw- 0 0 0 2790 Mar 7 2016 package/gulpfile.js
-rw-rw-rw- 0 0 0 1231 Mar 7 2016 package/LICENSE.BSD
-rw-rw-rw- 0 0 0 242 Mar 7 2016 package/.jshintrc
-rw-rw-rw- 0 0 0 29 Mar 7 2016 package/.babelrc
$
According to https://github.com/npm/registry/issues/120#issuecomment-276157329, old versions of npm didn't include README.md. If you upgrade your npm version, and publish a patch release of this module, the readme should appear on npmjs.com.
(issue markdown adapted from domenic/opener#24)
At https://www.npmjs.com/package/estraverse, it says there is no readme:
This is because the published package does not include README.md:
$ tar tvf $(npm pack estraverse) -rw-rw-rw- 0 0 0 1016 Mar 10 2016 package/package.json -rw-rw-rw- 0 0 0 27642 Mar 10 2016 package/estraverse.js -rw-rw-rw- 0 0 0 2790 Mar 7 2016 package/gulpfile.js -rw-rw-rw- 0 0 0 1231 Mar 7 2016 package/LICENSE.BSD -rw-rw-rw- 0 0 0 242 Mar 7 2016 package/.jshintrc -rw-rw-rw- 0 0 0 29 Mar 7 2016 package/.babelrc $According to https://github.com/npm/registry/issues/120#issuecomment-276157329, old versions of npm didn't include README.md. If you upgrade your npm version, and publish a patch release of this module, the readme should appear on npmjs.com.
(issue markdown adapted from domenic/opener#24)