Tee Ming

As of [[email protected]](https://github.com/sveltejs/kit/releases/tag/%40sveltejs%2Fadapter-cloudflare%405.0.0), SvelteKit no longer uses esbuild to bundle the build. This is because Cloudflare's Wrangler also bundles the worker code when you try to deploy the project. We...

> @eltigerchino I tried again including the entire build output (intially when I opened the issue I included only the `output` and `cloudfare` directories). > > As you can see...

It's possible to compile the `_worker.js` file through the `wrangler deploy --dry-run` [CLI command](https://developers.cloudflare.com/workers/wrangler/commands/#deploy), but it might be better if we had a Wrangler API to bundle the worker for...

Sorry this took a while. I think I've found a pretty satisfying fix that uses existing Cloudflare Wrangler behaviour. You can try out the fix before it's released by installing...

Had to [revert the PR](https://github.com/sveltejs/kit/pull/13622) as the build output was still missing the server dependencies. To get a build artefact, we'd need to bundle the server dependencies in a way...

> We only need to re-request the parent data on the server because there's no way to pass the parent data back into the load function endpoint when we call...

> Is a test still TODO or is it basically impossable to test? I chose not to add a test because it's only reproducible by breaking the prerender app build....

related to content negotiation https://github.com/sveltejs/kit/issues/11794

> Is this the right fix? Feels like maybe 405 is the wrong response for a `GET` request with `*/*` if a page exists. Thoughts? Agreed that this PR is...

Sorry about this one! One of the pages/workers predicates is returning falsely. The correct behaviour here is that the build should error and warn you that you need to have...