kit
kit copied to clipboard
web development, streamlined
> [!NOTE] > If SvelteKit v3 requires Node.js v20+, and Svelte v5 requires ES2023+, this issue can be converted to setting: > - `vite.config`'s `build.target` to `es2023` > - `tsconfig.json`'s...
### Describe the problem Importing `$env/dynamic/private` from `src/hooks.ts` throws an error about the import not supported in client side code, but it doesn't say that the error is coming from...
### Describe the problem When you `import { files } from '$service-worker'` and have numerous files in your static folder—such as country flags, icons, and unused assets that you keep...
### Describe the bug The Bug (or maybe a documentation issue?): I've exported `ssr=false` in my root +layout. If I import (via statement/top-level) in any sub-route's +page.js/.ts a dependency that...
### Describe the problem SvelteKit allows you to _visually_ deny access to a route using [server hooks](https://kit.svelte.dev/docs/hooks#server-hooks), but the compiled `+page.svelte`'s filename is always public as `.svelte-kit/output/client/_app/immutable/entry` has import references...
### Describe the bug Normally from navigating from page A to page B the callback flow is the following: 1. A - `beforeNavigate` 2. A - `onNavigate` 3. B -...
### Describe the bug  Since a dynamic script is required for starting the app in the builded version, it is not possible...
### Describe the problem Some module is large, but not compatible with SSR. So I can only import it dynamically in an `onMount` or `if (browser)` block. But I still...
### Describe the bug I have a PUT function inside of a +server.js file. If a file is uploaded to the server and it is not in a multipart form,...
### Describe the bug `+page.server.ts` should return HTTP 404: ``` import { error } from '@sveltejs/kit'; export const load = () => { error(404, 'Something went wrong'); return { pageData:...