kit icon indicating copy to clipboard operation
kit copied to clipboard

web development, streamlined

Results 1071 kit issues
Sort by recently updated
recently updated
newest added

### Describe the problem Currently, `__error.svelte` is hardwired to `__layout.svelte`. In several of my projects, I use `__layout.svelte` for non-trivial purposes, including authentication guards, and of course rendering part of...

enhancement

### Describe the bug I am building a SvelteKit SPA app that is using Authorization Code Flow with PKCE with Keycloak. I want to handle the auth redirect in the...

router

### Describe the problem It's a common scenario to have protected routes. It would be great if the docs would outline the best practice for doing this in sveltekit. ###...

documentation

### Describe the bug Hello, I'm not really sure if it is a bug or a misusage on my part, but since migrating to the new page system, I can't...

bug
p3-edge-case

### Describe the problem When building application-like websites, users expect instant feedback when changing pages, even if the page's content isn't ready yet. It's confusing to a user when they...

enhancement

### Describe the problem Simply, it would be necessary to accompany the SvelteKit documentation with a "UML Activity Diagram" that shows the passage of data (locals, data, ecc) between server...

documentation

### Describe the bug My app is using `svelte-adapter-static` with the `trailingSlash` option set to `'always'`, so each route is a folder containing its own index.html. I use a static...

Seems like `latest` and `next` are generally pointing to the same release in `@sveltejs` packages that haven't hit a stable v1, e.g. in [`@sveltejs/kit`](https://www.npmjs.com/package/@sveltejs/kit?activeTab=versions) & [`@sveltejs/adapter-auto`](https://www.npmjs.com/package/@sveltejs/adapter-auto?activeTab=versions), but they aren't in...

svelte-package

### Describe the bug When I use `afterNavigate`, `beforeNavigate` or `goto` in a `+page` while using the adapter static and the [chunking strategy](https://vitejs.dev/guide/build.html#chunking-strategy) of vite (`splitVendorChunkPlugin`) I get an error...

vite

### Describe the bug When routing from `/b` to `/` using an anchor element, the `/b/+page.svelte` component does not get unmounted. ```svelte import { page } from '$app/stores'; import {...

bug
router
blocked by upstream