That works for my use case, thanks

Okay, and what about Deno packages?

Deno packages are specific to the deno runtime so they won't work either.

And while you might find a non-nodejs email package, it also won't work. The issue here is that the Workers runtime doesn't proxy anything other than HTTP, so SMTP won't work.

Okay, ill try to use mailgun

are there any how-to guides on converting a worker to function for noobs?

Not so much a how-to but there's https://developers.cloudflare.com/pages/platform/functions/ - which has a section for converting a Worker. https://developers.cloudflare.com/pages/platform/functions/#migrating-from-workers

all we are doing is uploading or deleting an image from Cloudflare Images

addEventListener('fetch', event => {
  const { request } = event;
  const { url } = request;

  if (request.method === 'POST') {
    return event.respondWith(handleRequest(request));
  } else if (request.method === 'GET') {
    return event.respondWith(new Response(`The request was a GET`));
  }
});


/**
 * Many more examples available at:
 *   https://developers.cloudflare.com/workers/examples
 * @param {Request} request
 * @returns {Promise<Response>}
 */
async function handleRequest(request) {

  const authToken = await request.headers.get("authorization");

  const formData = await request.formData();

  const oldImageId = formData.get("old_image_id");

  formData.delete("old_image_id");

  const response = await fetch(
    `https://api.cloudflare.com/client/v4/accounts/63d719b39174eb1cfc9816ccf9a7512f/images/v1`,
    {
      method: "POST",
      body: formData,
      headers: {
        Authorization: `Bearer ######`,
      },
    }
  );

  await fetch(
    `https://api.cloudflare.com/client/v4/accounts/63d719b39174eb1cfc9816ccf9a7512f/images/v1/${oldImageId}`,
    {
      method: "DELETE",
      headers: {
        Authorization: `Bearer #######`,
      },
    }
  );

  return response;
}

but we can't get this to work in functions

How do I test functions locally with SvelteKit?

Do you mean manual tests or integration tests?

The dev server should Just Work for backend routes

i mean run dev server locally

yeah but, im getting confused by the "serve a folder of static assets"

i've used normal workers before, but unsure how to run the dev server locally with sveltekit

does the SvelteKit adapter do output of worker code into the ./dist folder?

actually lemme give that a try

The work there is done by

adapter-cloudflare

yep, it builds it into

.svelte-kit/cloudflare

very cool

but you should just be able to use

svelte-kit dev

, no need to build

unless you're using CF-specific stuff like KV or durable objects

i was thinking of using KV

you can run miniflare on the build output

but the way I do it is by mocking KV for development so I can still use

svelte-kit dev

ts
/** For development */
async function getDummyStore() {
  const { Miniflare } = await import("miniflare")
  const mf = new Miniflare({
    script: "",
    kvNamespaces: ["STORE"],
    kvPersist: true
  })
  return mf.getKVNamespace("STORE")
}

looks like a nice solution

Is it possible to add npm packages to be used in functions, and if so how?

Can anyone help point this functions noob in the right direction? We really want to move our rogue worker in to a function so it is packaged with the rest of our app

Has anyone had issues purging cache from functions? I add header

response.headers.set('Cloudflare-CDN-Cache-Control', 'public, max-age=120')

Which works fine, I see the age header on subsequent refreshes increment up to 120 then the page is fetched from origin again. But if I purge the cache, both `by url `and

purge everything

, it still increments up to 120 before fetching from origin again. I'd expect it to fetch from origin within the ~30s purge window. The only thing I notice is this response header

cf-cache-status: DYNAMIC

, this should be

HIT

right? (not sure why it's showing dynamic when it does cache successfully, my function just returns the current timestamp so I know it's working fine)

I can see static assets get cached and purged successfully, just the functions don't behave how I expect

So Functions shouldn't, AFAIK, have the cache applied in front of them.