@sveltejs/kit 2.22.3 → 2.22.5
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/package.json +1 -1
- package/src/exports/vite/index.js +9 -1
- package/src/version.js +1 -1
package/package.json
CHANGED
|
@@ -284,6 +284,9 @@ async function kit({ svelte_config }) {
|
|
|
284
284
|
`!${kit.files.routes}/**/+*server.*`
|
|
285
285
|
],
|
|
286
286
|
exclude: [
|
|
287
|
+
// Without this SvelteKit will be prebundled on the client, which means we end up with two versions of Redirect etc.
|
|
288
|
+
// Also see https://github.com/sveltejs/kit/issues/5952#issuecomment-1218844057
|
|
289
|
+
'@sveltejs/kit',
|
|
287
290
|
// exclude kit features so that libraries using them work even when they are prebundled
|
|
288
291
|
// this does not affect app code, just handling of imported libraries that use $app or $env
|
|
289
292
|
'$app',
|
|
@@ -297,7 +300,12 @@ async function kit({ svelte_config }) {
|
|
|
297
300
|
// that bundle later on from resolving the export conditions incorrectly
|
|
298
301
|
// and for example include browser-only code in the server output
|
|
299
302
|
// because they for example use esbuild.build with `platform: 'browser'`
|
|
300
|
-
'esm-env'
|
|
303
|
+
'esm-env',
|
|
304
|
+
// This forces `$app/*` modules to be bundled, since they depend on
|
|
305
|
+
// virtual modules like `__sveltekit/paths` (this isn't a valid bare
|
|
306
|
+
// import, but it works with vite-node's externalization logic, which
|
|
307
|
+
// uses basic concatenation)
|
|
308
|
+
'@sveltejs/kit/src/runtime'
|
|
301
309
|
]
|
|
302
310
|
}
|
|
303
311
|
};
|
package/src/version.js
CHANGED