Yup, I can confirm that

wrangler.toml

is ignored with Pages (and Functions).

With SvelteKit make sure you set either an environment variable called

NODE_VERSION

and a value of

16.7.0

, or add a file in your root folder called

.node-version

(no extension) with the contents of

16.7.0

does pages + functions make workers sites obsolete? I can't imagine a reason to use workers sites

Workers Sites was the early prototype of Pages, so yes, while still supported Pages is the recommended way to go.

Maybe a bit more for advanced path handling that can't be done with the headers file yet

alright, and about this

@sveltejs/adapter-cloudflare

, do I just add it to my

svelte.config.js

like this:

js
import adapter from '@sveltejs/adapter-cloudflare';

export default {
    kit: {
        adapter: adapter()
    }
};

and that's it?

Yeah, but Functions could be used for that.

Yup, that's it.

Then choose the

SvelteKit

preset when creating a Pages project.

And also:

Make sure you set either an environment variable called NODE_VERSION and a value of 16.7.0, or add a file in your root folder called .node-version (no extension) with the contents of 16.7.0

okay, but as I see my build folder is different here for some reason

Yeah, that's the expected build folder when building for Cloudflare.

If you build locally (

npm run build

) and you've got the adapter set up right you should have a

cloudflare

folder appear in there too.

I haven't added the adapter to my config file yet, so maybe that's why

Yeah, that's probably why.

what causes the

wrangler

command to take half a second or so to run? is that node starting up?

it worked

this is amazing

👍 SvelteKit on Functions is amazing.

how does caching work with Functions?

is it automatic?

Did you mean, "SvelteKit on Pages"?

SvelteKit on Pages Functions, yeah. 😄

Could someone point me to the documentation for this? I tried searching the Cloudflare docs, as well as google, but could only find the mention in

@User I don't think there's very much documentation on it. https://github.com/cloudflare/workers-types/blob/74c94f8f96fa427353acd60ebc00d910f8e7cdfe/index.d.ts#L1708

you can learn a lot from https://github.com/cloudflare/images.pages.dev

Ohh, thank you for the example!

is it (or will it be) possible to provide your own routing configuration? ie the JSON config that lives on the functions tab of a deployment:

{ "routes": { "/api": ... } }

etc reason - don't want to use full _worker.js to handle every request, but I have a couple routes that would ideally all be handled with a single module

When using SvelteKit with

adapter-cloudflare

maybe it's still considered Cloudflare Pages Functions but it's not using the

./functions

folder automation (routing, middleware, etc.). It's using SvelteKit's endpoint (not client-side UI) routing, middleware, etc. and compiling it down to an

_worker.js

file that seems to run as a Cloudflare worker. Yes, I know that when you use

./functions

it gets compiled down to a worker also but I think of that compiling as the primary (?only?) feature of "Functions" and when using SvelteKit with

adapter-cloudflare

you just aren't using that feature so it's hard for me to think of that as using "Functions". Makes sense?

It even bypasses the serving of static assets as documented here: https://developers.cloudflare.com/pages/platform/functions/#advanced-mode