Vscode extension oxlint not load config with vp v0.1.18

[RabbitShare]

Describe the bug

After vp create react-router try configure oxlint. But extension not working

vp lint works usually

Reproduction

any project created with vp v0.1.18

Steps to reproduce

No response

System Info

Environment:
  Version  24.14.1
  Source   lts

Tool Paths:
  node  /Users/user/.vite-plus/js_runtime/node/24.14.1/bin/node
  npm   /Users/user/.vite-plus/js_runtime/node/24.14.1/bin/npm
  npx   /Users/user/.vite-plus/js_runtime/node/24.14.1/bin/npx

oxc version:
Identifier    oxc.oxc-vscode
Version       1.52.0
Last Updated  2 weeks ago

Used Package Manager

npm

Logs

Validations

• Read the Contributing Guidelines.
• Check that there isn't already an issue for the same bug.
• Confirm this is a Vite+ issue and not an upstream issue (Vite, Vitest, tsdown, Rolldown, or Oxc).
• The provided reproduction is a minimal reproducible example.

[fengmk2]

I see oxc prompts in your screenshot, does this mean the oxc extension is working normally?

[RabbitShare]

It's show warning, but in rules typed "eslint/no-unused-vars": "error". I think oxc used default settings

With "eslint/no-unused-vars": "off" still show warning

[fengmk2]

@RabbitShare I can't reproduce this issue, I think restart the vscode IDE should works.

[nstepien]

I'm having the same issue, I'm on Windows if that matters.

In the Oxc (Lint) output:

2026-04-16 17:26:07.898 [info] Searching for oxlint binary.
2026-04-16 17:26:07.898 [info] Using server binary at: d:\repos\...\node_modules\oxlint\bin\oxlint
2026-04-16 17:26:07.898 [info] 2026-04-16T16:26:07.881474Z  INFO oxc_language_server::backend: initialize: Some([WorkspaceOption { workspace_uri: Uri(Uri { scheme: "file", authority: Some(Authority { userinfo: None, host: "", host_parsed: RegName(""), port: None }), path: "/d%3A/repos/...", query: None, fragment: None }), options: Object {"configPath": String("vite.config.ts"), "disableNestedConfig": Bool(false), "fixKind": String("safe_fix"), "run": String("onType"), "flags": Object {"disable_nested_config": String("false"), "fix_kind": String("safe_fix")}} }])
2026-04-16T16:26:07.881526Z  INFO oxc_language_server::backend: oxlint version: 1.60.0

2026-04-16 17:26:08.080 [info] 2026-04-16T16:26:07.989822Z  WARN oxlint::lsp::server_linter: Failed to load config: Failed to parse config from d:/repos/...\vite.config.ts

In the Oxc (Fmt) output:

2026-04-16 17:26:07.898 [info] Searching for oxfmt binary.
2026-04-16 17:26:07.898 [info] Using server binary at: d:\repos\...\node_modules\oxfmt\bin\oxfmt
2026-04-16 17:26:07.899 [info] 2026-04-16T16:26:07.888234Z  INFO tokio-rt-worker oxc_language_server::backend: initialize: Some([WorkspaceOption { workspace_uri: Uri(Uri { scheme: "file", authority: Some(Authority { userinfo: None, host: "", host_parsed: RegName(""), port: None }), path: "/d%3A/repos/...", query: None, fragment: None }), options: Object {"fmt.experimental": Bool(true), "fmt.configPath": String("vite.config.ts")} }])
2026-04-16T16:26:07.888300Z  INFO tokio-rt-worker oxc_language_server::backend: oxfmt version: 0.45.0

2026-04-16 17:26:08.080 [info] 2026-04-16T16:26:07.989829Z  WARN tokio-rt-worker oxfmt::lsp::server_formatter: Failed to build config resolver: d:\repos\...\vite.config.ts
Error: JS functions cannot be represented as a serde_json::Value
Ensure the file has a valid default export of a JSON-serializable configuration object., falling back to default config

My settings.json looks like this:

{
  "editor.codeActionsOnSave": {
    "source.fixAll.ts": "never",
    "source.removeUnusedImports": "explicit",
    "source.fixAll.oxc": "explicit",
    "source.format.oxc": "always"
  },
  "editor.defaultFormatter": "oxc.oxc-vscode",
  "editor.formatOnSave": false,
  "editor.formatOnSaveMode": "file",
  "js/ts.experimental.useTsgo": true,
  "oxc.configPath": "vite.config.ts",
  "oxc.fmt.configPath": "vite.config.ts",
  "oxc.path.tsgolint": "node_modules/.bin/tsgolint.cmd",
  "npm.scriptRunner": "vp"
}

(unrelated related, but tsoglint doesn't work if I don't manually specify the path with .cmd).

The Oxc extension has no issues loading vite.config.ts with vite-plus@0.1.16, but it has issues with 0.1.18, and I assume 0.1.17 as well.

[camc314]

@nstepien what does your vite.config.ts look like? does it export a function?

[nstepien]

My config looks like this, no functions:

import { defineConfig } from "vite-plus";

export default defineConfig({
  staged: {
    '*': 'vp check --fix',
  },

  lint: {
    options: {
      typeAware: true,
      typeCheck: true,
    },

    plugins: [
      'eslint',
      'import',
      'jsdoc',
      'jsx-a11y',
      'node',
      'oxc',
      'promise',
      'react-perf',
      'react',
      'typescript',
      'unicorn',
    ],

    rules: {
      '@typescript-eslint/no-floating-promises': 'off',
      '@typescript-eslint/restrict-template-expressions': 'off',
    },
  },

  fmt: {
    singleQuote: true,
    sortImports: true,
  },
});

With the following

• the formatter in the extension does not respect the settings, but Oxc (Fmt) does not log an error/warning
• vp fmt still works

export default {
  fmt: {
    singleQuote: true,
    sortImports: true,
  },
};

With the following

• the formatting in the extension respects the settings
• but that obviously breaks vp fmt

export default defineConfig({
  singleQuote: true,
  sortImports: true,
});

So it seems like the extension does not read the settings correctly with vite-plus@0.1.18, which is odd because I do not have issues with vite-plus@0.1.16