

We are now hiring remote roles in countries across North America, Europe, and Asia
async keyword when defining the functionexport const onRequestGet = async ({ request, next }) => {@sveltejs/adapter-cloudflare for cloudflare pages generates a _worker.js file, which means every page request is caught by the worker and counts towards my function requests which will eventually be billed?_worker.js file, so it’s the same behaviour regardless.onRequestGet will only respond to GET requests whereas onRequest will respond to all requests. Rest of it is just down to personal preference though. Should be functionally identical.wrangler pages dev at the moment.npx wrangler pages dev --remote to do?wrangler pages dev is entirely local. No builds are used when you’re testing with wrangler pages dev.asyncexport const onRequestGet = async ({ request, next }) => {@sveltejs/adapter-cloudflare_worker.js_worker.jsonRequestGetonRequestwrangler pages devwrangler pages devwrangler pages devnpx wrangler pages dev --remote