New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
@babel/core and babel-preset-current-node-syntax contain files with date older than 1980 #12501
@babel/core and babel-preset-current-node-syntax contain files with date older than 1980 #12501
Comments
Hey @BenoitAverty! We really appreciate you taking the time to report an issue. The collaborators on this project attempt to help as many people as possible, but we're a limited number of volunteers, so it's possible this won't be addressed swiftly. If you need any help, or just have general Babel or JavaScript questions, we have a vibrant Slack community that typically always has someone willing to help. You can sign-up here for an invite." |
Which version of those packages are you using? It should have already be fixed in both of them 🤔 |
Hey !
freshly installed with npm install. |
This could be a regression caused by #12453 |
The issue should be filed to https://github.com/nicolo-ribaudo/babel-preset-current-node-syntax
|
Bug Report
Current behavior
Babel contain some very old files.
To reproduce, install @babel/core and babel-preset-current-node-syntax on a fresh empty npm project, then run
find ! -newermt 1981-01-01
This gives the list of files older than January the first, 1980.
This is a problem when zipping the files because ZIP does not support timestamps that old. It happens, for example, when deploying an app to AWS
This seems to change based on the version of babel, for example, the latest babel-core has files from 1984 wheras the version used by @mdx-js has files from 1970.
Lastest
babel-preset-current-node-syntax
has some from before 1980.Possible Solution
As a workaround, uses can run
find ! -newermt 1981-01-01 -exec touch {} \
to fix the date. But it requires having diagnosed the problem.
The text was updated successfully, but these errors were encountered: