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

ESlint 9 #231

Merged
merged 8 commits into from
Dec 19, 2024
Merged

ESlint 9 #231

merged 8 commits into from
Dec 19, 2024

Conversation

jaap3
Copy link
Member

@jaap3 jaap3 commented Dec 10, 2024

  • Convert vue2 config
  • Convert vue3 config
  • Convert nuxt2 config
  • Convert nuxt3 config
  • Update package-lock.json
  • Update configuration to mention each config
  • Add automated tests
  • Test configs in AT project

Dropped Nuxt 2 support (not possible anymore, use the vue2 config for that if necessary).

Nuxt 3 has a module that configures eslint based on the project settings, which is more powerful than we can do with this package. Added instructions on how to integrate our overrides with the nuxt generated config.

Tested everything in the AT frontend monorepo, which has plain javascript, vue2, typescript and vue 3/nuxt subprojects.

@jaap3 jaap3 force-pushed the eslint-9 branch 4 times, most recently from a3e88a7 to ce76d7a Compare December 17, 2024 08:22
@jaap3 jaap3 force-pushed the eslint-9 branch 9 times, most recently from 26823eb to 3505f2a Compare December 17, 2024 13:42
@jaap3 jaap3 marked this pull request as ready for review December 17, 2024 15:19
@jaap3 jaap3 requested a review from dbunskoek as a code owner December 17, 2024 15:19
README.md Outdated Show resolved Hide resolved
README.md Show resolved Hide resolved
### Nuxt 3

Nuxt has its own ESLint module that configures ESLint based on the Nuxt project configuration. This generates a config
file that knows about the Nuxt project structure, layers, auto-imports, etc.
Copy link
Member

Choose a reason for hiding this comment

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

maybe mention the name / location of that config file here, so you more easily recognize it

Copy link
Member Author

Choose a reason for hiding this comment

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

I linked the docs (one line below), it don't think we need to repeat any of that in here.

README.md Outdated Show resolved Hide resolved
Copy link
Member

@dbunskoek dbunskoek left a comment

Choose a reason for hiding this comment

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

really nice work, love the testing approach

only remarks that I had are about consistently naming ESlint, not sure if we want to 'pull this straight' now

@jaap3
Copy link
Member Author

jaap3 commented Dec 17, 2024

really nice work, love the testing approach

only remarks that I had are about consistently naming ESlint, not sure if we want to 'pull this straight' now

I believe I now consistently call it ESLint in the README.

@jaap3
Copy link
Member Author

jaap3 commented Dec 17, 2024

Keeping this open until I'm completely done with the AT follow up, to make sure I don't need to follow up with a fixup PR/release.

@jaap3 jaap3 force-pushed the eslint-9 branch 3 times, most recently from 7ea72f4 to cdf0f25 Compare December 19, 2024 10:14
@jaap3 jaap3 merged commit 168a8e9 into main Dec 19, 2024
1 check passed
@jaap3 jaap3 deleted the eslint-9 branch December 19, 2024 12:53
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.

2 participants