-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
chore: clean up ESLint config post vitest
migration
#11135
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: clean up ESLint config post vitest
migration
#11135
Conversation
Thanks for the PR, @aryaemami59! 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 project configuration. |
View your CI Pipeline Execution ↗ for commit 1551966.
☁️ Nx Cloud last updated this comment at |
…t-eslint into chore/cleanup-eslint-config
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #11135 +/- ##
=======================================
Coverage 90.92% 90.92%
=======================================
Files 499 499
Lines 50845 50845
Branches 8384 8384
=======================================
Hits 46231 46231
Misses 4599 4599
Partials 15 15
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
…t-eslint into chore/cleanup-eslint-config
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.
Thanks!
…t-eslint into chore/cleanup-eslint-config
nx config wise this is a very confusing change tbh. Please can you share your reasoning? |
@JamesHenry why is it confusing? Or rather which part is confusing? I'm more than happy to elaborate. |
The mixed usage and application and then seeming upcoming undoing of things is why I wanted to understand the broader reasoning here. I think it's best if a publish a video on these concepts to bring us on the same page |
That was actually done by mistake I just fixed it. |
}, | ||
{ | ||
"plugin": "@nx/eslint/plugin", | ||
"include": ["packages/*"], | ||
"options": { | ||
"targetName": "lint" | ||
} |
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.
"@nx/eslint:lint": { | ||
"dependsOn": ["eslint-plugin-internal:build", "typescript-eslint:build"], | ||
"options": { | ||
"noEslintrc": true, | ||
"cache": true, | ||
"eslintConfig": "{workspaceRoot}/eslint.config.mjs" | ||
}, | ||
"outputs": ["{options.outputFile}"], | ||
"cache": 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.
Without this repo:lint
would not be cached unless We explicitly pass this configuration to the root project.json
file.
"eslint-plugin-internal:build", | ||
"typescript-eslint:build" | ||
], | ||
"dependsOn": ["eslint-plugin-internal:build", "typescript-eslint:build"], |
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.
We are only using typescript-eslint
and eslint-plugin-internal
inside the eslint.config.mjs
file, therefore eslint-plugin:build
is not needed here.
PR Checklist
eslint.config.mjs
postvitest
migration #11132Overview