kit
kit copied to clipboard
web development, streamlined
Call beforeNavigate once with type unload on external navigation Fixes #6726 Fixes #6770 Given the reasons in https://github.com/sveltejs/kit/issues/6726#issuecomment-1247106719 I think this is the most sensible thing to do ### Please...
### Describe the bug After migrating to the latest svelte version and following [this guide](https://github.com/sveltejs/kit/discussions/5774) to do so, I have noticed that all builds using [adapter-netlify](https://www.npmjs.com/package/@sveltejs/adapter-netlify) fail if the adapter...
### Describe the bug ...because it also applies to non-page requests (e.g. if you throw an error in `handle` or a `+server.js` file, it will go through `handleError`, and if...
### Describe the bug Basically, we have this `svelte.config.js`. ```js import adapter from '@sveltejs/adapter-node'; const config = { kit: { adapter: adapter(), paths: { base: '/basepath' }, } }; export...
### Describe the problem There should be a way to determine from within a load function inside a `+page.ts` file or `+layout.ts` whether the load function is being called for...
### Describe the problem The new actions and forms api is very good, but I was very surprised (probably misread the docs and migration guide) to find out that the...
### Describe the bug it works fine in dev mode, but with inlineStyleThreshold: 32 * 1024 and vite.build.assetsInlineLimit: 2 * 1024, the relative links to font files (e.g. .woff2) gets...
### Describe the bug Double execution of the page on the server side, at server startup, when the page is open in a web browser. ### Reproduction 1. use the...
### Describe the problem Currently matchers are placed in a seperate folder, away from the routes. ### Describe the proposed solution Place matchers in `+page.js` (or `+page.server js`) or even...
### Describe the problem If setting up a new sveltekit project via `npm create svelte@latest` and you request eslint support, you will by default get setup with https://github.com/sveltejs/eslint-plugin-svelte3 The issue...