CI: add ESLint - #8
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
…so lint reflects real issues, not env gaps
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Adds ESLint to CI, per the "do we have lint" follow-up.
eslint.config.js— flat config,js.configs.recommended+ a relaxedno-unused-vars(warn,_-prefixed args ignored).test/**excluded from linting for now.package.json—eslint+@eslint/jsdevDependencies,npm run lintscript.ci.yml— newLintstep (npm run lint) after the syntax check, before unit tests.package-lock.jsonviagenerate-lockfile.ymlto include the new devDependencies (npm ciwould otherwise fail on the mismatch).Existing source wasn't touched, so if
recommendedflags anything already in the codebase this PR will show it — that's expected, not a regression from this change.