I'd love to be able to use both svelte-kit dev and wrangler pages dev. I've tried

wrangler pages dev ./.svelte-kit/cloudflare -- svelte-kit dev

but that doesn't proxy the assets or the api correctly.

I'm about to try to launch them separately and sense that the cloudflare services are local, but I thought I'd ask first here in case someone has already figured this out.

Tried to test this out from the Blog on Cloudflare Pages.

Build fails due to Cloudflare node version being too old.

Is there anyway to build in own CI and push to CF Pages?

> [email protected] postinstall /opt/buildhome/repo/node_modules/esbuild
--
13:25:01.401 | > node install.js
13:25:01.401 |  
13:25:01.546 | npm WARN notsup Unsupported engine for @sveltejs/[email protected]: wanted: {"node":">=14.13"} (current: {"node":"12.18.0","npm":"6.14.4"})

This may be an issue for the sveltekit cloudflare adapter team but I'm wondering why this doesn't use the /functions convention for deploying to pages? In looking at the generated code, it's not actually clear to me how server-side functionality like the /todos.json endpoint is accomplished. Is it all in the _workers.js file?

How can you access secrets (runtime not client accessible environment variables) for Sveltekit API endpoints with cloudflare pages? Tested a couple of approaches, but can't figure it out unfortunately.

using url.pathname in load function throws error:
Method pathname called on incompatible receiver [object Object]

and adding headers to svelte config does not fix the problem:
https://kit.svelte.dev/docs#configuration-headers

is there another workaround?

Thanks

I'm having isssues deploying with wrangler to cloudflare pages.

can you write a bit

Any chance we could get a refresh on this repo? Lots of broken stuff with all the updates in sveltekit recently. Thanks!

Hello @lukeed how are you supposed to access environmental variables during runtime, I tried both process.env.ENV_NAME and just ENV_NAME and they both don't work, can you help me

Thanks