-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
chore: rename release.ts to release.mts #8204
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
chore: rename release.ts to release.mts #8204
Conversation
Thanks for the PR, @JoshuaKGoldberg! typescript-eslint is a 100% community driven project, and we are incredibly grateful that you are contributing to that community. The core maintainers work on this in their personal time, so please understand that it may not be possible for them to review your work immediately. Thanks again! 🙏 Please, if you or your company is finding typescript-eslint valuable, help us sustain the project by sponsoring it transparently on https://opencollective.com/typescript-eslint. |
✅ Deploy Preview for typescript-eslint ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
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.
Fun fact: jest.preset.js
listed at the bottom of tsconfig.eslint.json
has been deleted in 08ae2c41d, perhaps we can remove it from tsconfig?
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.
My point was addressed, but @auvred's seems to be important
Co-authored-by: auvred <61150013+auvred@users.noreply.github.com>
PR Checklist
issuePR followup: chore: use nx release #8194Overview
ESLint was unhappy with the idea of renaming
tools/release/release.ts
torelease.mts
becausetsconfig.eslint.json
doesn't allow including.mts
files.