Netlify

import adapter(alias) function adapter(opts?: AdapterOptions): Adapter
import adapter from '@sveltejs/adapter-netlify';
import { sveltekit(alias) function sveltekit(config?: Config): Promise<Plugin[]>
import sveltekit
The SvelteKit Vite plugin, which must be added to your vite.config.js file along with your project's configuration:
/// file: vite.config.js
import adapter from '@sveltejs/adapter-auto';
import { sveltekit } from '@sveltejs/kit/vite';
import { defineConfig } from 'vite';

export default defineConfig({
	plugins: [
		sveltekit({
			adapter: adapter(),
			compilerOptions: {
				experimental: {
					async: true
				}
			},
			experimental: {
				remoteFunctions: true
			}
		})
	]
});
As well as SvelteKit, the plugin options are used by other tooling that integrates with Svelte such as editor extensions.
Any options that don't belong to SvelteKit are passed through to vite-plugin-svelte, so you can set options like inspector here too. The experimental namespace is shared — SvelteKit reads its own flags and forwards the rest.

[!LEGACY]
Prior to SvelteKit 3, config lived in a svelte.config.js file, which is no longer supported. The ability to configure SvelteKit via vite.config.js was added in version 2.62.

reference } from '@sveltejs/kit/vite';
import { defineConfig(alias) function defineConfig(config: UserConfig): UserConfig (+5 overloads)
import defineConfig
Type helper to make it easier to use vite.config.ts
accepts a direct 
{@link 
UserConfig
}
 object, or a function that returns it.
The function receives a 
{@link 
ConfigEnv
}
 object.
 } from 'vite';

export default defineConfig(alias) defineConfig(config: UserConfig): UserConfig (+5 overloads)
import defineConfig
Type helper to make it easier to use vite.config.ts
accepts a direct 
{@link 
UserConfig
}
 object, or a function that returns it.
The function receives a 
{@link 
ConfigEnv
}
 object.
({
	plugins(property) UserConfig.plugins?: PluginOption[] | undefined
Array of vite plugins to use.
: [
		sveltekit(alias) sveltekit(config?: Config): Promise<Plugin[]>
import sveltekit
The SvelteKit Vite plugin, which must be added to your vite.config.js file along with your project's configuration:
/// file: vite.config.js
import adapter from '@sveltejs/adapter-auto';
import { sveltekit } from '@sveltejs/kit/vite';
import { defineConfig } from 'vite';

export default defineConfig({
	plugins: [
		sveltekit({
			adapter: adapter(),
			compilerOptions: {
				experimental: {
					async: true
				}
			},
			experimental: {
				remoteFunctions: true
			}
		})
	]
});
As well as SvelteKit, the plugin options are used by other tooling that integrates with Svelte such as editor extensions.
Any options that don't belong to SvelteKit are passed through to vite-plugin-svelte, so you can set options like inspector here too. The experimental namespace is shared — SvelteKit reads its own flags and forwards the rest.

[!LEGACY]
Prior to SvelteKit 3, config lived in a svelte.config.js file, which is no longer supported. The ability to configure SvelteKit via vite.config.js was added in version 2.62.

reference({
			adapter(property) Config.adapter?: Adapter | undefined
Your adapter is run when executing vite build. It determines how the output is converted for different platforms.
undefined
: adapter(alias) adapter(opts?: AdapterOptions): Adapter
import adapter({
				// See below for an explanation of these options
				edge(property) AdapterOptions.edge?: boolean | undefined
If true, your app will be deployed as a Netlify Edge Function rather than the standard Node-based function.
false
: false,
				split(property) AdapterOptions.split?: boolean | undefined
If true, your app will be split into multiple functions instead of a single one for the entire app.
false
: false,
				publish(property) AdapterOptions.publish?: string | undefined
The directory to write prerendered pages and static assets (the contents of static, plus client-side JS and CSS generated by SvelteKit) to.
'build'
7.0.0
: 'build'
			})
		})
	]
});

/** @type {import('./$types').PageServerLoad} */
export const load = async (event) => {
	const context = event.platform?.context;
	console.log(context); // shows up in your functions log in the Netlify app
};

import type { PageServerLoad } from './$types';

export const load: PageServerLoad = async (event) => {
	const context = event.platform?.context;
	console.log(context); // shows up in your functions log in the Netlify app
};

[build]
	command = "npm run build"
	publish = "build"

[functions]
	directory = "functions"