chore(ck-vscode): remove unused eslint setup#132
Merged
Conversation
ck-vscode shipped an \`npm run lint\` script + four eslint dev deps, but no eslint config file ever existed in the directory — running lint would have failed at startup. Nothing in CI runs it either. Removing the dead setup: - Drops 4 dev deps from package.json (eslint, @typescript-eslint/*) - Removes the lint script - Cleans .vscodeignore of the now-pointless .eslintrc.json pattern - Regenerated package-lock.json If someone wants lint in the future, the right starting point is a fresh \`eslint --init\` with the flat-config flow (which eslint 9+ requires anyway), not maintaining bumps on a tool nobody runs. Side effect: closes dependabot PRs #123 (@typescript-eslint/parser 7 → 8) and #124 (eslint 8 → 10) automatically, since their target deps no longer exist. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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.
Why
ck-vscode shipped:
...but no eslint config file ever existed in `ck-vscode/`. Running `npm run lint` would have failed at startup looking for one. Nothing in CI runs it either (`grep -rn 'npm run lint' .github/` is empty).
So we're maintaining version bumps on a tool nobody actually uses. Dependabot has been opening PRs against it (#123, #124) which all need flat-config migration work to land.
What this does
Verified
Side effects
Closes #123 and #124 automatically — the deps they bump no longer exist.
If lint comes back later
Start with a fresh `eslint --init` and the flat-config (`eslint.config.js`) flow. eslint 9+ requires it. Better than maintaining a stale legacy-config setup.
🤖 Generated with Claude Code