Skip to content

fix: force $app/* modules to be bundled #13977

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

Merged
merged 3 commits into from
Jul 9, 2025
Merged

fix: force $app/* modules to be bundled #13977

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
61b53b2
fix: force `$app/*` modules to be bundled
Rich-Harris Jul 9, 2025
81e4e3f
use a string
Rich-Harris Jul 9, 2025
dd5f2c1
OCD
Rich-Harris Jul 9, 2025
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
5 changes: 5 additions & 0 deletions .changeset/flat-eggs-start.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
---
'@sveltejs/kit': patch
---

fix: force `$app/*` modules to be bundled
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 @@ -297,7 +297,12 @@ async function kit({ svelte_config }) {
// that bundle later on from resolving the export conditions incorrectly
// and for example include browser-only code in the server output
// because they for example use esbuild.build with `platform: 'browser'`
'esm-env'
'esm-env',
// This forces `$app/*` modules to be bundled, since they depend on
// virtual modules like `__sveltekit/paths` (this isn't a valid bare
// import, but it works with vite-node's externalization logic, which
// uses basic concatenation)
'@sveltejs/kit/src/runtime'
]
}
};
Expand Down
Loading