Bug: comment mentionning eslint throws a parse error using jsonc.

[christophehurpeau]

Environment

ESLint version: 9.16.0
@eslint/json version: 0.8.0
Node version: 22

Which language are you using?

jsonc

What did you do?

Configuration

{
    name: "@pob/eslint-config/base/languages/json/plugins",
    plugins: { json },
  },

  // lint JSON files
  {
    name: "@pob/eslint-config/base/languages/json/json",
    files: ["**/*.json"],
    language: "json/json",
    // @ts-ignore
    ...json.configs.recommended,
  },

  // lint JSONC files
  {
    name: "@pob/eslint-config/base/languages/json/jsonc",
    files: ["**/*.jsonc", "**/tsconfig.json", ".vscode/*.json"],
    language: "json/jsonc",
    languageOptions: {
      allowTrailingCommas: true,
    },
    // @ts-ignore
    ...json.configs.recommended,
  },

jsonc file (it's a settings.json for vscode):

{
  // npm config
  "npm.packageManager": "yarn",
  // eslint config
  "eslint.workingDirectories": ["."]
}

What did you expect to happen?

No error

What actually happened?

Failed to parse JSON from 'config': Expected property name or '}' in JSON at position 1 (line 1 column 2)eslint

Link to Minimal Reproducible Example

none

Participation

• I am willing to submit a pull request for this issue.

Additional comments

The issue is because the comment starts with "eslint" so it's considered as an eslint instruction, but it's not the case here. I've tracked the error to be from:

const parseResult = commentParser.parseJSONLikeConfig(value);

[nzakas]

Yes, comments beginning with "eslint" are considered directives, so you can do this:

// eslint no-unsafe-values: error
{}

If you change the capitalization of "eslint" to "ESLint", you'll avoid this error.