I would have done "return object in javascript response"
I 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?
Smy main question was, xhr post works, right?
Sspecial reason = i already have xhr deployed so only little changes needed
SHow does one protect against a theoretical DDoS on my function?
SLike the 100k limit for the day would be magically gone
SIf it happens
BAre pages functions different than cloudflare workers? Ie: don't necessarily have feature parity (I'm new-ish to both)
BI'm interested in this concept as well - though I'm using React and not Vue, the principal is the same.
BJust thinking out loud here... I noticed for pages functions in "advanced mode", you have to serve your static assets in your functions with
return env.ASSETS.fetch(request); (see https://developers.cloudflare.com/pages/platform/functions/#advanced-mode). So at least in advanced mode it seems you could also proxy asset requests to another local development server (ie: create-react-app dev server running on port 3000). It would be a neat idea to add to wrangler2 to provide a local dev server url where you could both be debugging pages functions and running a framework dev server locally (that will later be compiled/transpiled to a bundled/minified production build before being published to pages). This I think describes the ask for people using React/Vue/Angular/etc.Documentation for Cloudflare Pages, the best way to deploy your static and JAMstack sites
EThey are mostly the same. Pages Functions basically compile/bundle down to Workers. The current limitations mean that you can't configure the Pages Functions Worker as completely yet as you can a regular Worker. So you can't yet set any compatibility date/flags..
And you can't deploy any Durable Objects inside your Pages repository. (Although you can bind a DO published by another Worker)..
And you can't deploy any Durable Objects inside your Pages repository. (Although you can bind a DO published by another Worker)..
SI'm interested in this too, i think using Next.js but essentially the same question
SAlso this 
