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 bug When requesting a page with `export const trailingSlash='always'`, Vercel returns a `308 Resume Incomplete` status. In browser this lead to a ERR_TOO_MANY_REDIRECTS error. Note that navigating...

pkg:adapter-vercel

### Describe the problem I'm implementing server-side analytics, and I'm using load functions to report user navigation. Some page: ```typescript export const load = (event) => { event.locals.trackNavigation(event); }; ```...

This PR solves #12200. Assets emitted from a vite-plugin cannot be loaded by the pre-renderer's fetch implementation because they are not listed in the server manifest. This PR detects files...

### Describe the problem When looking up information on how `404`s work for unknown routes, I ended up reading the docs about [+error.svelte](https://kit.svelte.dev/docs/routing#error). There it says: >If no route can...

### Describe the bug When switching pages, there is a bug happening when the layout contains some code to show a loading spinner on `$navigating != null` and the page...

### Describe the bug ## Overview Previously there was some discussion over the use of yarn PNP / berry here * https://github.com/sveltejs/kit/issues/993 The main advantage of PNP is that it...

contributions-welcome

### Describe the bug The application breaks on HMR update. The following message is presented in the console: ` Unrecoverable HMR error in : next update will trigger a full...

awaiting submitter

- Replace kleur with node:util's native styleText - Upgrade node minimum requirement from v18.13 to v20.13 Resolves: #12396 Creating as draft, to check if the node upgrade PR should be...

breaking change

### Describe the bug When navigating from page A to another, if a Tiptap textfield is _focused_, SvelteKit completely breaks. Instead of swapping the page, the new page is simply...

This PR aims to improve the documentation by explicitly stating that `use:enhance` is only compatible with forms using `method="POST"`. Despite the fact that using `use:enhance` with other methods should [throw...

documentation