Components: File dates of npm package are in the past (1985)

[rhalff]

Bug, feature request, or proposal:

Bug

What is the expected behavior?

(Build?) server has time configured correctly.

What is the current behavior?

Date is in the past (1985)

What are the steps to reproduce?

mkdir test
cd test
npm init -y
npm add @angular/cdk
ls -hal node_modules/@angular/cdk | head
total 228K
drwxr-xr-x 20 rhalff rhalff 4.0K Apr 25 19:32 .
drwxr-xr-x  3 rhalff rhalff 4.0K Apr 25 19:32 ..
drwxr-xr-x  3 rhalff rhalff 4.0K Apr 25 19:32 a11y
-rw-r--r--  1 rhalff rhalff  232 Oct 26  1985 a11y.d.ts
-rw-r--r--  1 rhalff rhalff  193 Oct 26  1985 a11y.metadata.json
-rw-r--r--  1 rhalff rhalff  181 Oct 26  1985 a11y-prebuilt.css
-rw-r--r--  1 rhalff rhalff  761 Oct 26  1985 _a11y.scss
drwxr-xr-x  3 rhalff rhalff 4.0K Apr 25 19:32 accordion
-rw-r--r--  1 rhalff rhalff  237 Oct 26  1985 accordion.d.ts

Same seems to be the case for @angular/material

@angular/cli does show the correct date.

What is the use-case or motivation for changing an existing behavior?

It's confusing. Especially when hunting for a bug in the same area.

Which versions of Angular, Material, OS, TypeScript, browsers are affected?

At least 5.2.5 and 6.0.0-rc.12

[rhalff]

Is this a convention or something for generated files? lodash among others seem to do the same.

e.g. find node_modules/ -type f -mtime +11680

I get the funny part, but not the why.

[LayZeeDK]

What's funny about that date?

Related: https://github.com/npm/npm/issues/20439

[rhalff]

@LayZeeDK

[josephperrott]

Closing as this is working as expected as we now use npm 6.0 see https://github.com/npm/npm/issues/20439 for npm's explanation.

[angular-automatic-lock-bot[bot]]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{_This action has been performed automatically by a bot._}