sveltejs/kit · error · Error

${source.errors[0].message}

Error message

${source.errors[0].message}

What it means

SvelteKit statically analyzes page options (like ssr/prerender exports) by parsing the module with acorn-typescript's parseSync. If the parser reports syntax errors, this error throws with the parser's first error message.

Source

Thrown at packages/kit/src/exports/vite/static_analysis/index.js:41

/**
 * Collects page options from a +page.js/+layout.js file, ignoring reassignments
 * and using the declared value (except for load functions, for which the value is `true`).
 * Returns `null` if any export is too difficult to analyse.
 * @param {string} filename The name of the file to report when an error occurs
 * @param {string} input
 * @returns {PageOptions | null}
 */
export function statically_analyse_page_options(filename, input) {
	// if there's a chance there are no page exports or an unparseable
	// export all declaration, then we can skip the AST parsing which is expensive
	if (!skip_parsing_regex.test(input)) {
		return {};
	}

	try {
		const source = parseSync(filename, input, { sourceType: 'module' });
		if (source.errors.length) throw new Error(source.errors[0].message);

		/** @type {Map<string, Extract<ESTree.Expression, { type: 'Literal' }>['value']>} */
		const page_options = new Map();

		for (const statement of source.program.body) {
			// ignore export all declarations with aliases that are not page options
			if (
				statement.type === 'ExportAllDeclaration' &&
				statement.exported &&
				!valid_page_options.has(get_name(statement.exported))
			) {
				continue;
			}

			if (
				statement.type === 'ExportDefaultDeclaration' ||
				statement.type === 'ExportAllDeclaration'
			) {

View on GitHub (pinned to 03f1687fe6)

Solutions

1. Fix the syntax error reported in the message in the referenced file
2. Ensure the file extension matches its language (.svelte.js vs .svelte.ts) so it parses correctly
3. Update @sveltejs/kit and vite plugin so the bundled parser supports your syntax
4. Temporarily rename the file to exclude it from page-option analysis to confirm the cause

Example fix

// before (src/routes/+page.svelte.ts)
export const prerender = = true; // syntax error
// after
export const prerender = true;

null

null

null // build-time error; fix syntax rather than catch

When it happens

Trigger: A .svelte.js/.svelte.ts module processed for page options contains syntax that the parser rejects (unsupported syntax, malformed code, invalid syntax for the configured lang), and the skip_parsing_regex did not skip the file.

Common situations: Syntax newer than the bundled parser supports; a file with mixed/inconsistent extensions; copy-pasted code with typos in page option modules; invalid regex-filtered module variants.

Related errors

• @sveltejs/enhanced-img requires @sveltejs/vite-plugin-svelte
• Expected to find metadata for remote file ${id}
• ${message}. Since you're using @sveltejs/adapter-auto, Svelt
• adapter-bun requires running the SvelteKit build with Bun. U
• ${log.message ?? String(log)}

AI-assisted analysis of sveltejs/kit@03f1687fe6 (2026-09-02). Data as JSON: /api/errors/e5f1a20f23b73dce. Report an issue: GitHub.