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

chore(CI): add tests for ESLint 8 #201

Closed
wants to merge 1 commit into from

Conversation

MichaelDeBoey
Copy link

@MichaelDeBoey MichaelDeBoey commented Aug 29, 2021

ESLint v8.0.0 is released 🎉

devDependency compatibility with ESLint 8:

@lydell lydell changed the title feat: support ESLint 8.x Test with ESLint 8.x and use it internally Oct 10, 2021
@MichaelDeBoey MichaelDeBoey force-pushed the eslint-8 branch 2 times, most recently from 058473e to 217f4f6 Compare October 13, 2021 18:18
@MichaelDeBoey MichaelDeBoey changed the title Test with ESLint 8.x and use it internally chore(CI): add tests for ESLint 8 Oct 13, 2021
coderbyheart added a commit to NordicSemiconductor/asset-tracker-cloud-eslint-config-typescript that referenced this pull request Oct 21, 2021
Because eslint-config-prettier does not yet support it.

See prettier/eslint-config-prettier#201
coderbyheart added a commit to NordicSemiconductor/asset-tracker-cloud-code-style-js that referenced this pull request Oct 21, 2021
Because eslint-config-prettier does not yet support it.

See prettier/eslint-config-prettier#201
@lampewebdev
Copy link

Any reason why this is a draft and can't be merged?

"doctoc": "2.0.0",
"eslint": "7.25.0",
"eslint": "^8.2.0",
Copy link

@Belco90 Belco90 Nov 15, 2021

Choose a reason for hiding this comment

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

If you stick to ESLint v7 in your dev dependencies, this PR could be merged without problems since the main changes for adding ESLint v8 compatibility to the package are already addressed in this very PR. Upgrading ESLint here is just for the local environment used to develop the project, that must not block this PR.

Copy link
Author

Choose a reason for hiding this comment

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

The package is still compatible with ESLint 7 (see tests), so it can still be merged even though we update the ESLint version for local development

Copy link

Choose a reason for hiding this comment

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

But there are some other ESLint plugins not compatible with v8 that can cause errors, that's why I'm suggesting not upgrading to v8 in dev dependencies so it doesn't block the release of the v8 compatibility 😅

Copy link
Member

Choose a reason for hiding this comment

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

block the release of the v8 compatibility

eslint-config-prettier already is (and always has been) compatible with ESLint 8. This PR is just adding tests for ESLint 8 and upgrading to using ESLint 8 internally. There’s no rush with this PR.

Marking as “unresolved” to increase visibility of this comment.

@@ -13,26 +13,30 @@ jobs:
strategy:
matrix:
os: [ubuntu-latest, windows-latest, macOS-latest]
node-version: [10.x, 12.x, 14.x, 15.x]
node: [10, 12, 14, 16]
eslint: [7, 8]

Choose a reason for hiding this comment

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

Node 10 probably needs to be excluded from the 8 matrix

lydell added a commit that referenced this pull request Jan 14, 2022
- Update to ESLint 8. (No need to test with ESLint 7 – we have never
  needed to test with multiple ESLint versions before, and ESLint 8
  changed nothing with the config system.)
- Update Prettier.
- Update all ESLint plugins. None of them had new conflicting rules.
- Update all other dependencies.
- Update Node.js versions to test with in CI: Drop Node.js 10 and 15
  since they are EOL. Add Node.js 16 and 17. Note:
  eslint-config-prettier still works with Node.js 10, and there’s no
  reason for that to change in the foreseeable future.
- Remove the table of contents in the readme. That’s a native GitHub
  feature these days.
- Update to npm lockfile version 2.
- Fix deprecation warning in build script.
- Fix lint errors from updated eslint-plugin-unicorn.

Supersedes and closes #201. (It was easier to do this myself than
reviewing that PR.)
@lydell lydell mentioned this pull request Jan 14, 2022
@lydell lydell closed this in #215 Jan 14, 2022
@MichaelDeBoey MichaelDeBoey deleted the eslint-8 branch January 14, 2022 23:46
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.

5 participants