`vp check --fix` formatting jsonc differently from Oxc VS Code extension

[nofxboy1234]

Describe the bug

I have the Vite Plus Extension Pack extension installed in vscode.
In a default fresh vite+ application, when I save tsconfig.json, the oxc vs code extension produces a different output to vp check --fix.

Reproduction

https://github.com/nofxboy1234/vp-temp2

Steps to reproduce

Open tsconfig.json with no trailing comma
Save in VS Code with Oxc formatter
Trailing comma gets added
Run vp check --fix
Trailing comma gets removed

System Info

vp env current:

VITE+ - The Unified Toolchain for the Web

Environment:
  Version  24.14.0
  Source   lts

Tool Paths:
  node  /home/dylan/.vite-plus/js_runtime/node/24.14.0/bin/node
  npm   /home/dylan/.vite-plus/js_runtime/node/24.14.0/bin/npm
  npx   /home/dylan/.vite-plus/js_runtime/node/24.14.0/bin/npx

vp --version:

VITE+ - The Unified Toolchain for the Web

vp v0.1.13

Local vite-plus:
  vite-plus  v0.1.13

Tools:
  vite             v8.0.1
  rolldown         v1.0.0-rc.10
  vitest           v4.1.0
  oxfmt            v0.41.0
  oxlint           v1.56.0
  oxlint-tsgolint  v0.17.1
  tsdown           v0.21.4

Environment:
  Package manager  pnpm v10.32.1
  Node.js          v24.14.0

Used Package Manager

pnpm

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.

[leaysgur]

NOTE: This will be fixed after oxfmt@0.42 is released and vite-plus is also updated.

[nofxboy1234]

NOTE: This will be fixed after oxfmt@0.42 is released and vite-plus is also updated.

Is this issue also related to ignorePatterns not being a valid option for fmt in vite.config.ts? It shows it in the config docs, but isn't recognized in vite config.

[leaysgur]

Not related.

But I think #1075 will fix it after next release.

[nofxboy1234]

Not related.

But I think #1075 will fix it after next release.

I see, thanks :)