Configure ESLint with flat config and StandardJS #4347
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thanks for taking a look. Note that there should not be both an NPM lock file and a PNPM lock file. PNPM should be the manager IIRC. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fix for issue #4288
Migrated the project to ESLint's new flat config system (
eslint.config.cjs), required as of ESLint v9. StandardJS was used as the base style guide, with a few adjustments to match Less.js's existing code style and avoid widespread formatting changes. Also added alintscript topackage.json.The project previously had no working ESLint configuration compatible with ESLint v9. This update brings the codebase into alignment with the latest ESLint standards and enables consistent, enforceable linting going forward.
Checklist:
This PR is designed to introduce linting with minimal disruption to the existing codebase. Further cleanup can be incremental once the config is in place.