https://discord.cloudflare.com logo
Join Discord
Powered by
# functions
  • l
    What does it do if you add a 
    [[path]].js
    or 
    [[path]].ts
    file in the 
    ./functions
    folder? Based upon this, I'm guessing that might then serve as your catch all: https://developers.cloudflare.com/pages/platform/functions/#functions-routing
  • i
    Yeah, so it's kind of like a Worker? But it doesn't actually bypass static asset serving. What happens (SvelteKit specific) internally is that, on build, your 
    _worker.js
    compiles a list of all of the static assets (like images, text files, etc) then on request it matches the request to that list and if it's a match it forwards it to Pages so that the static file is still served.
  • i
    Static files aren't bundled into the 
    _worker.js
    .
  • l
    You'd have to make sure it handled 404s and maybe even static assets though. I haven't tried it. If you can isolate those routes, maybe you could put them all under 
    ./functions/handle-special/[[path]].js
    ?
  • i
    Also, in my mind it's still a Function since it gets the inputs that are Pages specific, even if it lacks file-system routing.
  • l
    Another idea is to try doing what you need with middleware but I haven't tried that either: https://developers.cloudflare.com/pages/platform/functions/#adding-middleware
  • l
    Ohh, I didn't know that. What inputs are Pages specific?
  • i
    Haha, disregard that, I was thinking of regular Functions (non 
    _worker.js
    ) which get a 
    next
    that allows easier forwarding to the static file.
  • l
    That brings me full circle, except with more confidence. SvelteKit with 
    adapter-cloudflare
    is not really using Pages Functions. Just Pages. 🙂
  • i
    Well, if you want to get into the technical details, even static Pages is actually Workers, so. 😆
  • m
    Hi Larry. your explanation is not correct. if you use the /functions folder in a SvelteKit project, Cloudflare Pages ignores the Svelte app's .sveltekit/cloudflare/_worker.js entry point. I had already described this above. Also a possible solution (but here the developers of Cloudflare would have to do something.
  • i
    No, it's not a possible solution because of the architecture.
  • i
    When you use a 
    /functions
    folder Pages actually bundles it into a single 
    _worker.js
    for you, you just aren't aware.
  • i
    So using both a 
    _worker.js
    and 
    /functions
    would never be able to work.
  • m
    well, if it's wrapped in a _worker.js anyway, Clouflare could combine both _worker.js when using the framework preset for Svelekit.
  • i
    Not really, that's not how bundling works. There's a router built into Cloudflare's 
    _worker.js
    when using 
    /functions
    and also a completely different router for SvelteKit's 
    _worker.js
    that aren't compatible when used together.
  • m
    how about the other way around? if @sveltejs/adapter-cloudflare looks at the bundle if there is a function folder included and integrates the endpoints into the svelte worker?
  • i
    The APIs are very different; while it might be possible it's highly unlikely to ever work. I would instead urge you to use Endpoints; anything you can do in 
    /functions
    you can do in Endpoints.
  • m
    yes, i have also stayed away from it. i now use other independent workers that have written in rust and call them from the svelt app. is also ok!
  • l
    If the generated 
    _worker.js
    from SvelteKit is going to be ignored, why not use 
    adapter-static
    instead of 
    adapter-cloudflare
    ?
  • d
    the location data from the 
    cf
    object is invaluable. you can create really localized content. I wonder why this strategy isn't more prevalent
  • l
    Where is the 
    cf
    object?
  • k
    Should be under the request passed from the fetch handler - at least it is in a traditional worker
  • i
    CF is on 
    context.request
  • i
    (It's not standard, if you want typing information you'll need to use Cloudflare's types, forgot what they're called exactly)
  • w
    workers-types 😉
  • a
    that'd work if everything I needed to handle was behind a 
    /api
    , but I have a couple routes that are directly at the root, so I don't want to use a catch all. Vercel for example allows you to use a regex
  • a
    I see it's been asked a few times, but can't seem to figure out the correct way to see any logs from functions. Is it currently not possible?
  • j
    Not in production at this time unfortunately, sorry! It's definitely coming for when Functions hits GA though
  • j
    For now, I believe your only option is to use wrangler2 and debug locally
1...878889...392Latest