-
-
Notifications
You must be signed in to change notification settings - Fork 32
Closed
Labels
BREAKING CHANGEThis change will require a major version bumpThis change will require a major version bump
Description
Starting a list of my desired breaking changes, feedback welcome. We can perform this release once we have compiled enough changes.
Planned:
- Enable additional
recommended
rules:- feat!: enable
no-meta-replaced-by
,no-meta-schema-default
,require-meta-default-options
,require-meta-schema-description
asrecommended
rules #530 - Note: the new rule
require-meta-docs-recommended
is NOT intended to become arecommended
rule, so we won't enable this one.
- feat!: enable
- Change default rule options
- There don't appear to be any changes needed to default rule options this time.
- Supported Node.js versions
- Supported ESLint versions
- Migrations
For reference, V6 was released 2024-04-10 (CHANGELOG, discussion in #269).
AndreaPontrandolfo
Metadata
Metadata
Assignees
Labels
BREAKING CHANGEThis change will require a major version bumpThis change will require a major version bump
Type
Projects
Milestone
Relationships
Development
Select code repository
Activity
azat-io commentedon Feb 10, 2025
+1 for TS config support 👍
43081j commentedon Mar 19, 2025
yes please
we're currently in the process of moving quite a few eslint plugins to esm-only, so let me know if you want any help
drake-nathan commentedon Apr 6, 2025
TS or not, it should ship with types. If you're making a breaking change anyways, I would personally ship it in TS, ESM only, and ESLint >=9.
I'm happy to help with this effort!
michaelfaith commentedon Jun 14, 2025
Need any help with this work?
43081j commentedon Jun 14, 2025
here's the ESM conversion if its of any use:
main...43081j:eslint-plugin-eslint-plugin:esm-only
happy to open it as a PR if its a direction we want to go in
bmish commentedon Jun 15, 2025
Nice, yes I'd be interested in moving to both ESM and TypeScript (separately is fine). Would there be any user-facing impact from the ESM conversion?
43081j commentedon Jun 15, 2025
It should only affect people who use commonjs and node
<20
. But they can just migrate toeslint.config.mjs
without having to migrate their entire project, or they can use newer node.Other than that, everything should be pretty much the same
michaelfaith commentedon Jun 15, 2025
If #516 lands, i'd be happy to help with the migration to TypeScript, if needed.
michaelfaith commentedon Jun 20, 2025
Curious what you think about re-organizing the configs in this release, removing the
flat/
prefix. Would this be included in the plans to drop support for eslint v8?bmish commentedon Jun 20, 2025
We can remove the
flat/
prefix at this point and make flat the default.ESLint v9 was released over a year ago in April 2024. So I'm open to dropping ESLint v8/eslintrc support at this point if it will make our lives easier.
michaelfaith commentedon Jun 20, 2025
Great. I can take that up. I'd like to land that first before the typescript migration, since there'd be less cruft to migrate.
11 remaining items