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: target ESLint v9 #33

Merged
merged 1 commit into from
Oct 22, 2024
Merged

feat: target ESLint v9 #33

merged 1 commit into from
Oct 22, 2024

Conversation

Marsup
Copy link
Contributor

@Marsup Marsup commented Jul 27, 2024

This makes all rules and configs work with ESLint v9. I have not tried to keep it compatible with v8 as I'm not sure it's worth the effort. Some code (the rules) was automatically migrated by an eslint tool and is probably compatible with both versions though, so if we decide to keep backwards-compatibility, we probably just have to keep a duplicate of the old configs. As can be seen in lab's PR, I'm not sure how to properly handle the old .eslintignore behavior, so I went with passing it through labrc.

The CI will of course fail as it needs a compatible lab to work.

@Marsup Marsup added the breaking changes Change that can breaking existing code label Jul 27, 2024
@Marsup Marsup self-assigned this Oct 22, 2024
@Marsup Marsup added this to the 7.0.0 milestone Oct 22, 2024
@Marsup Marsup merged commit 3ec950a into master Oct 22, 2024
1 of 12 checks passed
@Marsup Marsup deleted the feat/target-eslint-9 branch October 22, 2024 13:40
@kanongil
Copy link
Contributor

The new version 7.0.0 seems to break tests, eg. here hapijs/bounce#38.

@Marsup
Copy link
Contributor Author

Marsup commented Oct 23, 2024

I know, it's because it's not supposed to be used with lab 25, but we put "*" out of laziness. Sadly, it's the case for many of our packages, I've updated bounce, you can rebase your branches, I'll update all the other packages.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breaking changes Change that can breaking existing code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants