You'll want to `JSON.stringify` the `body`, but otherwise yes 🙂
You'll want to 
JSON.stringifybody
SThanks, while sending (in this code) or while receiving?
ISending.
Scool
IYou can't directly put an Object body into a response, you'll need to
JSON.stringify(body)so the new body will be this?
body = JSON.stringify(body)
body = JSON.stringify(body)
IYup.
Salso, what is the widest possible class of this code that I can google so that I can find reusable code?
JS functions? Node.js functions? What should give me reusable code while also ensuring max possible userbase?
JS functions? Node.js functions? What should give me reusable code while also ensuring max possible userbase?
Si feel really awkward asking everything on this channel even though y'all are really nice
G“Pure JS” for the general day-to-day is usually what I search for. Or “web API” if I’m needing something specific about how to access request/response sort of stuff.
GThe MDN docs are brilliant
Syeah MDN is the MVP 
Sso how would you have googled my previous question, for example?
IEven some Node.JS stuff will work, as long as it doesn't import any node-js specific packages.
Syeah pure js then i guess
II would have done "return object in javascript response"
Soh cool
Ian Object is what the
{key: value}cool
Sthanks
Sso if I want to get back my json on client side, what would you change in this code?
async function fetchProductsAsJSON() {
const response = await fetch('https://mydomain.com/api/hello');
// waits until the request completes...
console.log(response);
}
fetchProductsAsJSON();
Kconst json = await response.json()
Sthanks and how would you have googled this if you were me?
Kmdn response jsonmdn fetchcool, thanks
Kalthough in the context of code running in Workers or Functions, it's not 1:1 the fetch you'll see on MDN
KDocumentation for Cloudflare Workers, a serverless execution environment that allows you to create entirely new applications or augment existing ones without configuring or maintaining infrastructure.
Kit's like 90% the same but there's a few bits here and there that aren't in Workers
Sis there a porting guide?
Kit's mostly a few things from the
initThe global fetch() method starts the process of fetching a
resource from the network, returning a promise which is fulfilled once the response is
available.
resource from the network, returning a promise which is fulfilled once the response is
available.
Kthere's no mode/credentials/etc on Workers
Sthen how auth headers get sent?
Ksame as any other header
Soh cool
KSthanks
Si can access environment vars in functions code, right?
S(without leaking them, i hope)
IYup, it'll be on
context.env.VARIABLE_NAMEthanks
BI'm using sveltekit with functions (with adapter-auto so sveltekit endpoints are the functions now), but I am having trouble accessing env vars when testing locally. I am using wrangler:
However,
The code works fine in production when deployed to cloudflare. On the guide for setting it up, it says to use wrangler to test it locally, but
However,
platformplatform.envThe code works fine in production when deployed to cloudflare. On the guide for setting it up, it says to use wrangler to test it locally, but
platform
JCall
next()context.next()Or you can
const file = await next()HTMLRewritermaybe technically it could fail if KV or something is entirely down... but I wouldn't worry about it in your context
Shi CF team,
if i POST via xhr on client side, will i be able to receive via onRequest on CF functions?
if i POST via xhr on client side, will i be able to receive via onRequest on CF functions?