I'm opening this issue because:

• npm is crashing.
• npm is producing an incorrect install.
• npm is doing something I don't understand.
• npm is producing incorrect or undesirable behavior.
• Other (see below for feature requests):

What's going wrong?

I noticed that the npm docs show "Last modified October 26, 1985" on some pages. For example here is the footer of the folders doc page:

I was curious why that would be the case and it looks like the v6.0.0 was published with those incorrect modification dates for a number of files:

$ npm install npm@6.0.0
...
$ ls -lah node_modules/npm/doc/files/npm-folders.md
-rw-r--r--  1 coryforsyth  staff   7.6K Oct 26  1985 node_modules/npm/doc/files/npm-folders.md

There are a number of files at the root of the installed npm package with the incorrect modification date as well. When the docs are built, they use that incorrect modification date. This is reported at the docs site, too: https://github.com/npm/docs/issues/990.

How can the CLI team reproduce the problem?

Install npm@6.0.0, look at last-modification time for the files.

supporting information:

• npm -v prints: 5.8.0
• node -v prints: v8.2.1
• npm config get registry prints: http://registry.npmjs.org/
• Windows, OS X/macOS, or Linux?: macOS
• Network issues:
  • Geographic location where npm was run: NYC
  • I use a proxy to connect to the npm registry.
  • I use a proxy to connect to the web.
  • I use a proxy when downloading Git repos.
  • I access the npm registry via a VPN
  • I don't use a proxy, but have limited or unreliable internet access.
• Container:
  • I develop using Vagrant on Windows.
  • I develop using Vagrant on OS X or Linux.
  • I develop / deploy using Docker.
  • I deploy to a PaaS (Triton, Heroku).