LSP loads vite.config.ts with the server's cwd as root
Maintainers usually reply within 1 day
@leaysgur is already working on this.
Since Oct 23, 2026.
Assessment
This issue has not been assessed yet.
Description
Describe the bug
oxlint/oxfmt load vite.config.ts without a root (apps/shared/src-js/vite_plus_config.ts):
resolveConfig({ configFile: path }, "build")
Vite falls back to process.cwd(). In a multi-root workspace (oxc-project/oxc-vscode#418) that's another repo, so plugins resolve against it. TanStack Start fails:
Could not resolve entry for router entry: router in app-a/src
The failing project is plain Vite (no vite-plus), so lazyPlugins() from #1756 isn't available.
Fix: resolveConfig({ root: dirname(path), configFile: path }, "build").
Reproduction
No repo. Steps below.
Steps to reproduce
- Workspace with a Vite+ repo first, then a Vite + TanStack Start repo.
- Open in VS Code with the Oxc extension.
- Loading the second repo's config fails.
System Info
vp v1.3.0 (vite 8.3.4, oxlint 1.88.0, oxfmt 0.73.0)
Node 24.22.1, bun 1.4.4, macOS 27.0.1
Oxc VS Code 1.64.1
Used Package Manager
bun
Logs
Failed to load config: app-c/vite.config.ts
Error: Could not resolve entry for router entry: router in app-a/src
at resolveEntry (@tanstack/start-plugin-core/dist/esm/resolve-entries.js:30:45)
at BasicMinimalPluginContext.config (@tanstack/start-plugin-core/dist/esm/vite/plugin.js:55:29)
at runConfigHook (app-a/.../@voidzero-dev/vite-plus-core/dist/vite/node/chunks/...)
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.
- Dominant language
- Rust
- Stars
- 6.5k
- Forks
- 296
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 229
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from voidzero-dev/vite-plus
-
Docker guide: the runtime stage needs libatomic1 for Node.js 25 and laterPossibly taken @kshanxs claimed this 1 day ago. Opendocumentation
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
voidzero-dev/vite-plus#3219 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
-
pending triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
voidzero-dev/vite-plus#2882 · 2 comments ·
Maintainers usually reply within 1 day
-
vp run -r executes each package task twice when the root package has a matching recursive scriptPossibly taken @wan9chi claimed this 2 days ago. Openpending triage
voidzero-dev/vite-plus#3221 · 1 comment · 1 assignee ·
Maintainers usually reply within 1 day
-
pending triage
Difficulty 4/5 3-5 days Newbie friendliness 48/100
voidzero-dev/vite-plus#3218 ·
Maintainers usually reply within 1 day
-
vp migrate doesn't flag esbuild-specific config (minify: "esbuild") — migrated project fails to build on Vite 8Possibly taken @john-okeefe claimed this 4 days ago. Opencontribution welcome
voidzero-dev/vite-plus#3176 · 1 reaction · 1 assignee ·
Maintainers usually reply within 1 day
All issues in voidzero-dev/vite-plus
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
Maintainers usually reply within 1 day
-
C-bug needs-triage O-UEFI T-libs
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
bug priority: P3 ready-for-agent
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
shep-pm/shep-kelpie#1332 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
ramensoftware/windhawk#1156 · 2 comments ·
-
area/cli complexity:trivial good first issue Stellar Wave test
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Externalize-Labs/externalize#23 ·
Maintainers usually reply within 1 day