Sync kit next docs

apps/svelte.dev/content/docs/kit/20-core-concepts/60-remote-functions.md

@@ -1116,7 +1116,7 @@ import { requested, query } from '$app/server';
 export const getPosts = query('unchecked', ({ filter }) => {
 	return ['foo', 'bar'];
 });
----cut---
+// ---cut---
 for (const { arg, query, ignore } of requested(getPosts, 10)) {
 	if (arg.filter === 'author:santa') {
 		void query.refresh();
@@ -1146,9 +1146,13 @@ await requested(getPosts, 1).refreshAll();
 If you want to intentionally ignore every selected update, use `ignoreAll`:
 
 ```js
-import { requested } from '$app/server';
+import { requested, query } from '$app/server';
+
+export const getPosts = query('unchecked', ({ filter }) => {
+	return ['foo', 'bar'];
+});
 
----cut---
+// ---cut---
 await requested(getPosts, 10).ignoreAll();
 ```
 

apps/svelte.dev/content/docs/kit/25-build-and-deploy/40-adapter-node.md

@@ -39,6 +39,8 @@ node build
 
 Development dependencies will be bundled into your app using [Rolldown](https://rolldown.rs/). To control whether a given package is bundled or externalised, place it in `devDependencies` or `dependencies` respectively in your `package.json`.
 
+Client assets and prerendered output are served from a list of files recorded during the build.
+
 ### Compressing responses
 
 You will typically want to compress responses coming from the server. If you're already deploying your server behind a reverse proxy for SSL or load balancing, it typically results in better performance to also handle compression at that layer since Node.js is single-threaded.
@@ -183,7 +185,7 @@ The directory to build the server to. It defaults to `build` — i.e. `node buil
 
 ### precompress
 
-Enables precompressing using gzip and brotli for assets and prerendered pages. It defaults to `true`.
+Generates `.br` and `.gz` variants of client and prerendered assets during the build. The server negotiates `Accept-Encoding` per request, preferring brotli over gzip, and each variant carries its own ETag. It defaults to `true`.
 
 ### envPrefix
 

apps/svelte.dev/content/docs/kit/25-build-and-deploy/90-adapter-vercel.md

@@ -7,6 +7,8 @@ To deploy to Vercel, use [`adapter-vercel`](https://github.com/sveltejs/kit/tree
 
 This adapter will be installed by default when you use [`adapter-auto`](adapter-auto), but adding it to your project allows you to specify Vercel-specific options.
 
+If you'd like to try out SvelteKit on Vercel, you can start from one of the [Vercel SvelteKit templates](https://vercel.com/templates/svelte).
+
 ## Usage
 
 Run [`npx sv add sveltekit-adapter="adapter:vercel"`](/docs/cli/sveltekit-adapter), or install with `npm i -D @sveltejs/adapter-vercel` and add the adapter to your `vite.config.js`:

apps/svelte.dev/content/docs/kit/60-appendix/35-migrating-to-sveltekit-3.md

@@ -500,6 +500,9 @@ await myCache.match(request);
 
 - bundling now happens with `rolldown`
 - the `ORIGIN` environment variable is removed (set `paths.origin` in your Vite config instead)
+- static assets are served from a list recorded at build time; files added to the output directory afterwards are not served, and replaced ones keep their old size and `ETag` (use environment variables for runtime configuration)
+- `ETag`s for static assets are content hashes, and `Last-Modified` is no longer sent
+- only `GET` and `HEAD` requests are served static assets; other methods result in a 405 response
 
 ### `adapter-netlify`