Cloudflare Project fails to build if a previously build output is in the `.sveltekit` folder

[paoloricciuti]

Since we do wrangler types --check before building when a cloudflare project is built locally the wrangler types generation changes if the .sveltekit folder has the build output inside.

BEFORE BUILD

/* eslint-disable */
// Generated by Wrangler by running `wrangler types` (hash: 4f9fe9ddb2ea1e2c41e1be5910da8551)
// Runtime types generated with workerd@1.20260518.1 2026-05-20 nodejs_als
interface __BaseEnv_Env {
	ASSETS: Fetcher;
}
declare namespace Cloudflare {
	interface Env extends __BaseEnv_Env {}
}
interface Env extends __BaseEnv_Env {}

// Begin runtime types
/*! *****************************************************************************
Copyright (c) Cloudflare. All rights reserved.
Copyright (c) Microsoft Corporation. All rights reserved.

AFTER BUILD

/* eslint-disable */
// Generated by Wrangler by running `wrangler types` (hash: c2abdaaa333fde981ecf28696abe73c4)
// Runtime types generated with workerd@1.20260518.1 2026-05-20 nodejs_als
interface __BaseEnv_Env {
	ASSETS: Fetcher;
}
declare namespace Cloudflare {
	interface GlobalProps {
		mainModule: typeof import("./.svelte-kit/cloudflare/_worker");
	}
	interface Env extends __BaseEnv_Env {}
}
interface Env extends __BaseEnv_Env {}

// Begin runtime types
/*! *****************************************************************************
Copyright (c) Cloudflare. All rights reserved.
Copyright (c) Microsoft Corporation. All rights reserved.

as you can see there's this extra part

/* eslint-disable */
// Generated by Wrangler by running `wrangler types` (hash: c2abdaaa333fde981ecf28696abe73c4)
// Runtime types generated with workerd@1.20260518.1 2026-05-20 nodejs_als
interface __BaseEnv_Env {
	ASSETS: Fetcher;
}
declare namespace Cloudflare {
+	interface GlobalProps {
+		mainModule: typeof import("./.svelte-kit/cloudflare/_worker");
+	}
	interface Env extends __BaseEnv_Env {}
}
interface Env extends __BaseEnv_Env {}

// Begin runtime types
/*! *****************************************************************************
Copyright (c) Cloudflare. All rights reserved.
Copyright (c) Microsoft Corporation. All rights reserved.

Since --check runs the generation and checks with the old one this means that

pnpm gen
pnpm build
pnpm build

will result in the second build to fail.

Even worse, if you regenerate the types and then push the build will break the deployment because the build output will not be present.

[teemingc]

Yeah, this is an unfortunate bug due to how Cloudflare deployments work at the moment. wrangler.jsonc's main key currently points to the build output but in other projects it points to the source. It's also the only way to tell Cloudflare Workers where our server entry point lives.

For what it's worth, this won't be an issue in SvelteKit 3 because it will point to the source file instead and uses a different config for deployment that's generated by the Cloudflare Vite plugin

[teemingc]

Changing the generation command to

		"gen": "wrangler types && node -e 'const fs=require(\"fs\");const f=\"worker-configuration.d.ts\";fs.writeFileSync(f,fs.readFileSync(f,\"utf8\").replace(/\\n\\tinterface GlobalProps \\{[\\s\\S]*?\\n\\t\\}/,\"\"))'"

might be an ok interim solution to cut out the unwanted part

[manuel3108]

Reopening, PR shouldnt have been merged yet