chore: export base
config from eslint-config-eslint
#18119
Merged
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.
Prerequisites checklist
What is the purpose of this pull request? (put an "X" next to an item)
[ ] Documentation update
[ ] Bug fix (template)
[ ] New rule (template)
[ ] Changes an existing rule (template)
[ ] Add autofix to a rule
[ ] Add a CLI option
[ ] Add something to the core
[x] Other, please explain:
Refs eslint/eslint.org#512 (comment)
Adds
base
export in theeslint-config-eslint
package.Configs exported from the main and cjs entry points are intended for files that run in Node.js, and therefore cannot be readily used for files that don't run in Node.js, like browser scripts or modules that will be bundled for use in browsers, as we have in the
eslint/eslint.org
project.What changes did you make? (Give an overview)
Added the new export in package.json, and updated README with an example of when and how to use it.
Is there anything you'd like reviewers to focus on?