Skip to content

editor: oxc_language_server does not enable parse_regular_expression parser option #9957

@fairbanksg

Description

@fairbanksg

What version of Oxlint are you using?

0.16.1

What command did you run?

VS Code extension

What does your .oxlintrc.json config file look like?

{
  "$schema": "./node_modules/oxlint/configuration_schema.json",

  "env": {
    "browser": true,
    "node": true,
    "es2022": true
  },

  "plugins": [
    "node",
    "eslint",
    "oxc",
    "unicorn",
    // "import",
    "typescript",
    "react",
    "react-perf",
    "jsx-a11y",
    "vitest",
    "nextjs"
  ],

  "rules": {
    "eqeqeq": "error",
    "react/rules-of-hooks": "error",
    "react/exhaustive-deps": "error",
    "eslint/no-unused-vars": [
      "error",
      {
        "varsIgnorePattern": "^_",
        "argsIgnorePattern": "^_",
        "caughtErrorsIgnorePattern": "^_",
        "ignoreRestSiblings": true
      }
    ]
  },

  "categories": {
    "correctness": "error"
    // "perf": "warn",
    // "suspicious": "warn"
  },

  "overrides": [
    {
      "files": ["**/*.spec.{ts,tsx,js,jsx}"],
      "rules": {
        "typescript/no-non-null-assertion": "off",
        "typescript/no-non-null-asserted-optional-chain": "off"
      }
    }
  ],

  "ignorePatterns": ["e2e/**/*", "codemods/**/*", "scripts/**/*"]
}

What happened?

I noticed a mismatch in the lint errors I was getting between oxlint and the VS Code extension.
When I run oxlint cli with this config, I get eslint(no-useless-escape) error on this regex: /([^\/]+)/g.
However, the VS Code extension does not show this as an error.

After digging around a bit, I saw that oxc_language_server does not enable the parse_regular_expression in oxc_parser, and if I do so, the extension begins reporting the error.

Metadata

Metadata

Assignees

Labels

Type

Priority

None yet

Effort

None yet

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions