.configs/eslint.config.v9.mjs looks like a leftover from the @cldmv/jsonv monorepo that wasn't fully split when this extension was extracted into its own repo. It's dead/broken here, and the filename carries a version suffix it shouldn't. Two things to address (not urgent — surfaced during v4 onboarding).
1. Incomplete monorepo split — orphaned/broken config
Evidence this config neither belongs to nor works in this repo:
- Its header says
@Project: @cldmv/jsonv (the parent monorepo), not this extension.
- It imports
../plugins/eslint-plugin-jsonv/dist/index.mjs — a path that does not exist in this repo.
eslint is not in devDependencies, and there is no lint script, so nothing runs this config.
Resolve by either (a) wiring ESLint up properly for this repo — add the dep + a lint script + a self-contained config with no cross-repo ../plugins/... imports — or (b) removing it. Note this extension is a declarative grammar/language package (package.json main: null, only syntaxes/*.tmLanguage.json + language-configuration.json, no JS source), so there is effectively nothing to lint — (b) is likely the right call.
2. Filename shouldn't include .v9
ESLint 9's flat config is conventionally just eslint.config.mjs; the ESLint major version doesn't belong in the filename. If the config is kept, rename eslint.config.v9.mjs → eslint.config.mjs.
Context
Found during CLDMV v4 onboarding. Because this repo has no analyzable JS/TS source (the only .js-family file is this stray ESLint config), CodeQL couldn't run and codeql.yml was dropped from the workflow set — see the modernize PR. This cleanup is independent of that and non-blocking.
.configs/eslint.config.v9.mjslooks like a leftover from the@cldmv/jsonvmonorepo that wasn't fully split when this extension was extracted into its own repo. It's dead/broken here, and the filename carries a version suffix it shouldn't. Two things to address (not urgent — surfaced during v4 onboarding).1. Incomplete monorepo split — orphaned/broken config
Evidence this config neither belongs to nor works in this repo:
@Project: @cldmv/jsonv(the parent monorepo), not this extension.../plugins/eslint-plugin-jsonv/dist/index.mjs— a path that does not exist in this repo.eslintis not indevDependencies, and there is nolintscript, so nothing runs this config.Resolve by either (a) wiring ESLint up properly for this repo — add the dep + a
lintscript + a self-contained config with no cross-repo../plugins/...imports — or (b) removing it. Note this extension is a declarative grammar/language package (package.jsonmain: null, onlysyntaxes/*.tmLanguage.json+language-configuration.json, no JS source), so there is effectively nothing to lint — (b) is likely the right call.2. Filename shouldn't include
.v9ESLint 9's flat config is conventionally just
eslint.config.mjs; the ESLint major version doesn't belong in the filename. If the config is kept, renameeslint.config.v9.mjs→eslint.config.mjs.Context
Found during CLDMV v4 onboarding. Because this repo has no analyzable JS/TS source (the only
.js-family file is this stray ESLint config), CodeQL couldn't run andcodeql.ymlwas dropped from the workflow set — see the modernize PR. This cleanup is independent of that and non-blocking.