Route level config not working for `+server.js`

[Smirow]

Describe the bug

Route level config seems to be ignored for +server.js/ts

Reproduction

Deploy to Vercel with a route level config in +server.js/ts.

Logs

No response

System Info

No response

Severity

annoyance

Additional Information

No response

[Rich-Harris]

'Reproduction' is not an optional field.

If this relates to ISR, there is a known issue we are currently investigating.

[Smirow]

@Rich-Harris I thought that was pretty self-explanatory, but I guess it's not: https://github.com/Smirow/kit-issue-8908

Should create two lambdas as I defined a config in api/+server.ts :

export const config: Config = {
  memory: 512,
  split: true // not needed
};

But when deployed to Vercel (or built for Vercel) it is bundled with the other route. So it seems that config is getting ignored in routes defined by +server.ts files (as opposed to +page(.server).ts, ...).

[Smirow]

So probably related to this as config are retrieved only if the route is a page:
EDIT: actually it may also come from upstream.

kit/packages/kit/src/core/postbuild/analyse.js

Lines 94 to 130 in 48bdb02

	if (route.page) {
	const nodes = await Promise.all(
	[...route.page.layouts, route.page.leaf].map((n) => {
	if (n !== undefined) return manifest._.nodes[n]();
	})
	);
	const layouts = nodes.slice(0, -1);
	const page = nodes.at(-1);
	for (const layout of layouts) {
	if (layout) {
	validate_common_exports(layout.server, route.id);
	validate_common_exports(layout.universal, route.id);
	}
	}
	if (page) {
	methods.add('GET');
	if (page.server?.actions) methods.add('POST');
	validate_page_server_exports(page.server, route.id);
	validate_common_exports(page.universal, route.id);
	}
	const should_prerender = get_option(nodes, 'prerender');
	prerender =
	should_prerender === true ||
	// Try prerendering if ssr is false and no server needed. Set it to 'auto' so that
	// the route is not removed from the manifest, there could be a server load function.
	// People can opt out of this behavior by explicitly setting prerender to false
	(should_prerender !== false && get_option(nodes, 'ssr') === false && !page?.server?.actions
	? 'auto'
	: should_prerender ?? false);
	config = get_config(nodes);
	}

[msonnb]

Can confirm that if I specify runtime: nodejs18.x in a +server.ts file, the route still shows up inside .svelte-kit/vercel-tmp/fn-0/manifest.js whereas it doesn't if I do the same inside +page.ts.

envinfo:

System:
    OS: macOS 13.1
    CPU: (8) arm64 Apple M1 Pro
    Memory: 47.92 MB / 16.00 GB
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 18.14.0 - ~/.n/bin/node
    Yarn: 1.22.19 - ~/Library/pnpm/yarn
    npm: 9.3.1 - ~/.n/bin/npm
  Browsers:
    Firefox Developer Edition: 110.0
    Safari: 16.2
  npmPackages:
    @sveltejs/adapter-vercel: 2.0.1 => 2.0.1 
    @sveltejs/kit: 1.5.0 => 1.5.0 
    svelte: 3.55.1 => 3.55.1 
    vite: 4.1.1 => 4.1.1