Skip to content
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

feat: use eslint 9 #9119

Open
wants to merge 27 commits into
base: v8
Choose a base branch
from
Open

Conversation

abrahamguo
Copy link
Contributor

PR Checklist

Overview

Use eslint@9 internally.

@typescript-eslint
Copy link
Contributor

Thanks for the PR, @abrahamguo!

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.

Copy link

netlify bot commented May 18, 2024

Deploy Preview for typescript-eslint ready!

Name Link
🔨 Latest commit 0319a55
🔍 Latest deploy log https://app.netlify.com/sites/typescript-eslint/deploys/6661aae7f6892e0008d0d283
😎 Deploy Preview https://deploy-preview-9119--typescript-eslint.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
Lighthouse
Lighthouse
1 paths audited
Performance: 94 (🔴 down 5 from production)
Accessibility: 100 (no change from production)
Best Practices: 92 (no change from production)
SEO: 90 (🔴 down 8 from production)
PWA: 80 (no change from production)
View the detailed breakdown and full score reports

To edit notification comments on pull requests, go to your Netlify site configuration.

@abrahamguo abrahamguo marked this pull request as draft May 18, 2024 22:41
@abrahamguo abrahamguo marked this pull request as ready for review May 22, 2024 01:50
@bradzacher
Copy link
Member

bradzacher commented May 22, 2024

We should delete this CI job

eslint_v9_tests:
name: Run tests on ESLint v9
needs: [build]
runs-on: ubuntu-latest
steps:
- name: Checkout
uses: actions/checkout@v4
- name: Install
uses: ./.github/actions/prepare-install
with:
node-version: ${{ env.PRIMARY_NODE_VERSION }}
- name: Build
uses: ./.github/actions/prepare-build
- run: yarn add eslint@9
- name: Run tests
run: yarn test
env:
CI: true

have we got an existing integration test to check for regressions on eslint v8?


converting to draft until CI is passing.

@bradzacher bradzacher marked this pull request as draft May 22, 2024 11:48
@bradzacher bradzacher added this to the 8.0.0 milestone May 22, 2024
@abrahamguo
Copy link
Contributor Author

@bradzacher there are currently no integration or CI tests for eslint 8. I can add one if you want, but do you feel that's necessary since we ask for eslint 9 in both our peerDependencies and devDependencies?

Doesn't seem like anything similar was added for eslint 7 when we moved from eslint 7=>8 (#3737)

Also, seems unrelated to this PR since this is about using eslint 9 internally

@bradzacher
Copy link
Member

Looks like there's already an integration test for v8 - https://github.com/typescript-eslint/typescript-eslint/tree/main/packages/integration-tests/fixtures/eslint-v8
So nothing to add!

Also, seems unrelated to this PR since this is about using eslint 9 internally

By moving to v9 internally our CI is no longer running against v8 - so we lose the test coverage asserting that we don't regress v8 compat.

But given we have the above integration test - we still have enough coverage.
It's not a super exhaustive test but it'll do (it's the same integration test coverage we maintained when we migrated to v8 internally)

@mattbrannon
Copy link

Just wanted to point out that one of your Netlify jobs has been running for nearly a week.
https://github.com/typescript-eslint/typescript-eslint/pull/9119/checks?check_run_id=25428243220

@abrahamguo
Copy link
Contributor Author

@mattbrannon that's nothing compared to #8673, whose job has been running for 3 weeks 😉

It does seem like that specific job sometimes hangs indefinitely. Not sure why

Abban added a commit to wmde/fundraising-banners that referenced this pull request Jun 4, 2024
Note: The typescript eslint plugin isn't ready for
eslint v9 yet, so we need to keep it at v8 for now

See: typescript-eslint/typescript-eslint#9119
Abban added a commit to wmde/fundraising-app-frontend that referenced this pull request Jun 4, 2024
Note: The typescript eslint plugin isn't ready for
eslint v9 yet, so we need to keep it at v8 for now

See: typescript-eslint/typescript-eslint#9119
Abban added a commit to wmde/fundraising-app-frontend that referenced this pull request Jun 4, 2024
Note: The typescript eslint plugin isn't ready for
eslint v9 yet, so we need to keep it at v8 for now

See: typescript-eslint/typescript-eslint#9119
@abrahamguo abrahamguo marked this pull request as ready for review June 6, 2024 13:05
['deprecation']: deprecationPlugin,
// https://github.com/gund/eslint-plugin-deprecation/issues/85
// https://github.com/typescript-eslint/typescript-eslint/issues/8988
['deprecation']: fixupPluginRules(deprecationPlugin),
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

TODO: looks like this got fixed — try it out

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants