-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
chore: use nx release #8194
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: use nx release #8194
Conversation
Thanks for the PR, @JamesHenry! 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. |
@@ -16,7 +16,6 @@ | |||
"executor": "@nx/eslint:lint", | |||
"outputs": ["{options.outputFile}"], | |||
"options": { | |||
"lintFilePatterns": ["packages/ast-spec/**/*.{mts,cts,ts,tsx}"], |
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.
The patterns are no longer required, the source files of the project are all eligible to be linted
@typescript-eslint/triage-team any idea why I am getting these integration-test failures? |
@@ -1,8 +1,3 @@ | |||
# Change 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.
[Question] While we're here, can we change it to # Changelog
? I don't know of any other project that uses two words 😄
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.
Ha yeah true
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.
Awesome to see the Lerna->Nx migration come to a head! 🚀
Requesting changes on moving things to repo-tools
and updating the last mention of Lerna from the docs. But I can aquiese if you don't think those should be blocking. 😄
void (async () => { | ||
try { |
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.
[Suggestion] We can avoid these wrappings by changing the file extension to .mts
and adding .mts
to tsconfig.eslint.json
.
void (async () => { | |
try { |
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.
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.
It's tsconfig.eslint.json
explicitly including only .ts
files in this folder, not .mts
.
@JoshuaKGoldberg any thoughts on the failures? |
@JoshuaKGoldberg @auvred updated per the PR feedback and now everything is passing except for the TSServer tests for eslint-plugin. I reran it in case it was flakiness, but the failure seems to be consistent. Any ideas please? |
Ah cool thanks, pressing ahead with this then while I still have time to focus on it |
For right now, a pinned header at the top of the changelog file is not supported, so I have removed this in every case to avoid confusion once we do the first release after this goes in:
I'll add support for a pinned header like that into
nx release
after this and we can bring it back if we want