Bun servers

bun add -D @sveltejs/adapter-bun

import import adapteradapter from '@sveltejs/adapter-bun';
import { function sveltekit(config?: Config): Promise<Plugin[]>
The SvelteKit Vite plugin, which must be added to your vite.config.js file along with your project’s configuration:
vite.config
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 mode

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.
referencesveltekit } from '@sveltejs/kit/vite';
import { function defineConfig(config: UserConfig): UserConfig (+5 overloads)
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.
defineConfig } from 'vite';

export default function defineConfig(config: UserConfig): UserConfig (+5 overloads)
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.
defineConfig({
	UserConfig.plugins?: PluginOption[] | undefined
Array of vite plugins to use.
plugins: [
		function sveltekit(config?: Config): Promise<Plugin[]>
The SvelteKit Vite plugin, which must be added to your vite.config.js file along with your project’s configuration:
vite.config
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 mode

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.
referencesveltekit({
			Config.adapter?: Adapter | undefined
Your adapter is run when executing vite build. It determines how the output is converted for different platforms.
@default
undefinedadapter: import adapteradapter()
		})
	]
});

bun run --bun build

bun ./build

import import adapteradapter from '@sveltejs/adapter-bun';
import { function sveltekit(config?: Config): Promise<Plugin[]>
The SvelteKit Vite plugin, which must be added to your vite.config.js file along with your project’s configuration:
vite.config
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 mode

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.
referencesveltekit } from '@sveltejs/kit/vite';
import { function defineConfig(config: UserConfig): UserConfig (+5 overloads)
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.
defineConfig } from 'vite';

export default function defineConfig(config: UserConfig): UserConfig (+5 overloads)
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.
defineConfig({
	UserConfig.plugins?: PluginOption[] | undefined
Array of vite plugins to use.
plugins: [
		function sveltekit(config?: Config): Promise<Plugin[]>
The SvelteKit Vite plugin, which must be added to your vite.config.js file along with your project’s configuration:
vite.config
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 mode

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.
referencesveltekit({
			Config.adapter?: Adapter | undefined
Your adapter is run when executing vite build. It determines how the output is converted for different platforms.
@default
undefinedadapter: import adapteradapter({
				out: stringout: 'build',
				envPrefix: stringenvPrefix: '',
				
serverOptions: {
    idleTimeout: number;
}serverOptions: {
					idleTimeout: numberidleTimeout: 30
				},
				
buildOptions: {
    sourcemap: string;
}buildOptions: {
					sourcemap: stringsourcemap: 'external'
				}
			})
		})
	]
});

import adapteradapter({ envPrefix: stringenvPrefix: 'MY_APP_' });

MY_APP_HOST=127.0.0.1 MY_APP_PORT=4000 bun ./build

import adapteradapter({
	
buildOptions: {
    compile: boolean;
}buildOptions: {
		compile: booleancompile: true
	}
});

bun run --bun build
./build/server

import adapteradapter({
	out: stringout: 'dist',
	
buildOptions: {
    compile: {
        outfile: string;
        target: string;
    };
    minify: boolean;
    bytecode: boolean;
    sourcemap: string;
}buildOptions: {
		
compile: {
    outfile: string;
    target: string;
}compile: {
			outfile: stringoutfile: 'application',
			target: stringtarget: 'bun-linux-x64'
		},
		minify: booleanminify: true,
		bytecode: booleanbytecode: true,
		sourcemap: stringsourcemap: 'linked'
	}
});

HOST=127.0.0.1 PORT=4000 bun ./build

SOCKET_PATH=/tmp/sveltekit.sock bun ./build

PROTOCOL_HEADER=x-forwarded-proto \
HOST_HEADER=x-forwarded-host \
PORT_HEADER=x-forwarded-port \
bun ./build

ADDRESS_HEADER=true-client-ip bun ./build

ADDRESS_HEADER=x-forwarded-for XFF_DEPTH=2 bun ./build

/** @type {import('./$types').RequestHandler} */
export function 
function GET({ getClientAddress, platform }: {
    getClientAddress: any;
    platform: any;
}): ResponseGET({ getClientAddress: anygetClientAddress, platform: anyplatform }) {
	return 
var Response: {
    new (body?: BodyInit | null, init?: ResponseInit): Response;
    prototype: Response;
    error(): Response;
    json(data: any, init?: ResponseInit): Response;
    redirect(url: string | URL, status?: number): Response;
}
The Response interface of the Fetch API represents the response to a request.
MDN Reference
Response.function json(data: any, init?: ResponseInit): Response
The json() static method of the Response interface returns a Response that contains the provided JSON data as body, and a Content-Type header which is set to application/json. The response status, status message, and additional headers can also be set.
MDN Reference
json({
		address: anyaddress: getClientAddress: anygetClientAddress(),
		serverId: anyserverId: platform: anyplatform.server.id,
		pendingRequests: anypendingRequests: platform: anyplatform.server.pendingRequests,
		pendingWebSockets: anypendingWebSockets: platform: anyplatform.server.pendingWebSockets
	});
}

var process: NodeJS.Processprocess.NodeJS.Process.on(event: string | symbol, listener: (...args: any[]) => void): NodeJS.Process (+13 overloads)
Adds the listener function to the end of the listeners array for the event
named eventName. No checks are made to see if the listener has already
been added. Multiple calls passing the same combination of eventName and
listener will result in the listener being added, and called, multiple times.
server.on('connection', (stream) => {
  console.log('someone connected!');
});
Returns a reference to the EventEmitter, so that calls can be chained.
By default, event listeners are invoked in the order they are added. The emitter.prependListener() method can be used as an alternative to add the
event listener to the beginning of the listeners array.
import { EventEmitter } from 'node:events';
const myEE = new EventEmitter();
myEE.on('foo', () => console.log('a'));
myEE.prependListener('foo', () => console.log('b'));
myEE.emit('foo');
// Prints:
//   b
//   a
@since
v0.1.101
@param
eventName The name of the event.
@param
listener The callback functionon('sveltekit:shutdown', async (reason: anyreason) => {
	await jobs.stop();
	await db.close();
});