feat!: support eslint v10 #507
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request updates documentation and configuration files to introduce and document a new
allconfiguration that enables all rules, and to clarify usage of themixed-esm-and-cjsconfig. It also updates examples to use the latest ESLint flat config format and improves the clarity and consistency of rule documentation.The most important changes are:
Documentation updates for new configs:
allconfiguration, including its symbol 🌐 in the rules table and config list, and clarified that it enables all rules but is not recommended for production use. [1] [2] [3] [4] [5] [6] [7]README.mdto use the newmixed-esm-and-cjsconfiguration (now without theflat/prefix), and updated code samples to use the modern ESLint flat config with ESM syntax. [1] [2]Configuration file changes:
.eslint-doc-generatorrc.jsto ignore the newmixed-esm-and-cjsconfig and removed emoji mappings for several flat configs, reflecting the new config structure. [1] [2]These changes make it easier for users to understand and use the new
allandmixed-esm-and-cjsconfigurations, and ensure that documentation and configuration files are consistent with the latest ESLint best practices.