Skip to content

Oxfmt and Oxlint Jetbrains plugins are not working with projects created by vp #3376

Closed

Description

@danny900714

Describe the bug

I created a Vite+ library project and checked the JetBrains options in the editor question. After I opened the created project in WebStorm, the Jetbrain's Oxfmt and Oxlint plugins failed to start.

Reproduction

nil

Steps to reproduce

  1. Create a project with vp create, and select pnpm, no coding agent, JetBrains, init git repo, set up pre-commit hook.
  2. Open the project in WebStorm
  3. Open src/index.ts
  4. The Oxfmt and Oxlint plugin failed indicators will show up at the bottom-right corner.

System Info

- `vp env current`

VITE+ - The Unified Toolchain for the Web

Node.js:
  Version    24.22.2
  Source     system PATH
  Bin Path   /opt/homebrew/bin/node
  Installed  true
  Mode       system_first

Package Manager:
  Name       pnpm
  Version    12.18.0
  Source     system PATH
  Bin Paths  
    pnpm     /opt/homebrew/bin/pnpm
    pnpx     /opt/homebrew/bin/pnpx
  Installed  true
  Mode       system_first

- `vp --version`

VITE+ - The Unified Toolchain for the Web

vp v1.5.0

Local vite-plus:
  vite-plus  v1.5.0

Tools:
  vite             v8.3.5
  rolldown         v1.2.16
  vitest           v5.1.0
  oxfmt            v0.76.0
  oxlint           v1.91.0
  oxlint-tsgolint  v7.0.2005
  tsdown           v0.23.4

Environment:
  Package manager  pnpm v12.18.0
  Node.js          v26.13.0

Used Package Manager

pnpm

Logs

Oxfmt plugin:

node:internal/modules/cjs/loader:1568
  throw err;
  ^

Error: Cannot find module '/Users/danny/Projects/danny900714/check-upstream-release/node_modules/vite-plus/bin/oxfmt'
    at Module._resolveFilename (node:internal/modules/cjs/loader:1564:15)
    at wrapResolveFilename (node:internal/modules/cjs/loader:1118:27)
    at defaultResolveImplForCJSLoading (node:internal/modules/cjs/loader:1142:10)
    at resolveForCJSWithHooks (node:internal/modules/cjs/loader:1169:12)
    at Module._load (node:internal/modules/cjs/loader:1341:5)
    at wrapModuleLoad (node:internal/modules/cjs/loader:261:19)
    at Module.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:154:5)
    at node:internal/main/run_main_module:33:47
 {
  code:
'MODULE_NOT_FOUND'
,
  requireStack: []
}

Node.js v24.22.2
StdIO connection closed
Exit code: 1
Command line: /opt/homebrew/bin/node /Users/danny/Projects/danny900714/check-upstream-release/node_modules/vite-plus/bin/oxfmt --lsp


Oxlint plugin:

node:internal/modules/cjs/loader:1568
  throw err;
  ^

Error: Cannot find module '/Users/danny/Projects/danny900714/check-upstream-release/node_modules/vite-plus/bin/oxlint'
    at Module._resolveFilename (node:internal/modules/cjs/loader:1564:15)
    at wrapResolveFilename (node:internal/modules/cjs/loader:1118:27)
    at defaultResolveImplForCJSLoading (node:internal/modules/cjs/loader:1142:10)
    at resolveForCJSWithHooks (node:internal/modules/cjs/loader:1169:12)
    at Module._load (node:internal/modules/cjs/loader:1341:5)
    at wrapModuleLoad (node:internal/modules/cjs/loader:261:19)
    at Module.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:154:5)
    at node:internal/main/run_main_module:33:47
 {
  code:
'MODULE_NOT_FOUND'
,
  requireStack: []
}

Node.js v24.22.2
Exit code: 1
Command line: /opt/homebrew/bin/node /Users/danny/Projects/danny900714/check-upstream-release/node_modules/vite-plus/bin/oxlint --lsp
StdIO connection closed

Validations

Activity

  1. added theissue type on Nov 7, 2026
  2. leaysgur commented on Nov 7, 2026

    @leaysgur
    Contributor

    Cannot find module '/Users/danny/Projects/danny900714/check-upstream-release/node_modules/vite-plus/bin/oxfmt'

    vite-plis/bin/oxlint|oxfmt was removed recently. #2672

    Instead, intellij plugin should search vp bin and start LSP. oxc-project/oxc-intellij-plugin#599

    Please update plugin and retry. If issue still happens, create new issue on extension repo.

  3. danny900714 commented on Nov 7, 2026

    @danny900714
    Author

    Thanks for pointing out the root cause. I think it is due to the plugin compatibility issue with IntelliJ 2026.3 version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

Fields

Priority

None yet

Effort

None yet

Target date

None yet

Start date

None yet

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions