`vp check --fix` fails to load oxlint plugin

[Mrahmani71]

Describe the bug

Running vp check --fix throws an error before lint analysis starts.

Formatting still completes successfully, but linting fails entirely.

vite.config.ts

import { defineConfig } from "vite-plus";

export default defineConfig({
 staged: {
 "*": "vp check --fix",
 },
 fmt: {},
 lint: {
 jsPlugins: [{ name: "vite-plus", specifier: "vite-plus/oxlint-plugin" }],
 rules: { "vite-plus/prefer-vite-plus-imports": "error" },
 options: { typeAware: true, typeCheck: true },
 },
});

Reproduction

https://github.com/Mrahmani71/test-viteplus

Steps to reproduce

1. Create a new project

vp create

2. Run the check command

vp check --fix

3. Observe the lint startup failure

VITE+ - The Unified Toolchain for the Web

error: Linting could not start
Failed to parse oxlint configuration file.

 × Failed to load JS plugin: vite-plus/oxlint-plugin
 │ "./oxlint-plugin" is not exported under the conditions ["module-sync", "node", "import"] from package D:/projects/000\node_modules\vite-plus (see exports field in D:/projects/000\node_modules\vite-plus\package.json)

Linting failed before analysis started
pass: Formatting completed for checked files (4.0s)

System Info

OS: Windows 11
IDE: Zed 1.3.6
----
Local vite-plus:
 vite-plus v0.1.21

Tools:
 vite v8.0.11
 rolldown v1.0.0
 vitest v4.1.5
 oxfmt v0.48.0
 oxlint v1.63.0
 oxlint-tsgolint v0.22.1
 tsdown v0.22.0

Environment:
 Package manager pnpm v11.2.2
 Node.js v24.16.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.

[jong-kyung]

Thanks for the report!

This looks related to #1408, which added the bundled Oxlint JS plugin at vite-plus/oxlint-plugin and the vite-plus/prefer-vite-plus-imports rule.

Could you upgrade to vite-plus@0.1.22?

If the same issue still happens after upgrading to 0.1.22, please let us know and we’ll take another look.

[Mrahmani71]

Yes, this issue has been fixed in version 0.1.22. I didn’t realize that pnpm had installed an older version because of minimumReleaseAge.