Skip to content

fix: ignore paths.base under Vitest to avoid vite-node module resolution failures #15715

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
MukundaKatta wants to merge 1 commit into
base: main
Choose a base branch
from
Open

fix: ignore paths.base under Vitest to avoid vite-node module resolution failures #15715

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions .changeset/fix-vitest-base-path-conflict.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,7 @@
---
'@sveltejs/kit': patch
---

fix: don't apply `paths.base` to Vite config when running under Vitest

When `kit.paths.base` was set to a prefix of the project's filesystem path (e.g. `/Users`), Vite would strip that prefix from the URLs vite-node uses to fetch modules over HTTP, causing `ERR_MODULE_NOT_FOUND` failures. Under Vitest, `base` is now forced to `/` so module resolution works regardless of the configured base path.
7 changes: 6 additions & 1 deletion packages/kit/src/exports/vite/index.js
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -988,7 +988,12 @@ async function kit({ svelte_config }) {
} else {
new_config = {
appType: 'custom',
base: kit_paths_base,
// When running under Vitest, don't apply kit.paths.base — vite-node
// serves filesystem modules over HTTP and Vite will strip the base
// prefix from those URLs, breaking module resolution when the base
// happens to match the start of the project path (e.g. "/Users").
// See https://github.com/sveltejs/kit/issues/13737
base: process.env.VITEST ? '/' : kit_paths_base,
build: {
rollupOptions: {
// Vite dependency crawler needs an explicit JS entry point
Expand Down
Loading