-
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
fix: Accidentally published tsconfig files
#16917
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
Conversation
|
Build successful! You can test your changes in the REPL here: https://babeljs.io/repl/build/58154 |
| "./babel.js", | ||
| "./babel.js.map", | ||
| "./babel.min.js", | ||
| "./babel.min.js.map" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nicolo-ribaudo
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you have any idea of why we started accidentally publishing them?
#16430 |
| @@ -1,3 +1,4 @@ | |||
| src | |||
| test | |||
| *.log | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I suggest we keep the *.log here. In circumstances where we have to manually publish npm packages and the first publish attempt is failed, npm will generate a debug log npm-debug.log, if we forget to remove that during the second publish attempt, this log will be unfortunately published.
tsconfig files
tsconfig filestsconfig files

We actually publish
tsconfig.jsonand eventsconfig.tsbuildinfofor all packages.🤦♂️