The /dist is for your static assets, the /functions folder is for your Pages function (https://devel

The /dist is for your static assets, the /functions folder is for your Pages function (https://developers.cloudflare.com/pages/functions/get-started/#create-a-function). Your structure sounds reasonable to me.

Ttexan The /dist is for your static assets, the /functions folder is for your Pages fun...

Keebs•2/28/25, 9:11 PM

would you look at something for me - there is this problem with mongodb not wokring on workers, which is being fixed right now - does that apply to pages too?
ref: https://github.com/cloudflare/workerd/discussions/2721

Keebs•2/28/25, 9:12 PM

I was looking at adding the polyfills someone created:
https://github.com/jchoi2x/cf-mongodb-polyfills
but then "wrangler pages dev" throws me an error:

  ✘ [ERROR] No matching export in
  "node_modules/cf-mongodb-polyfills/src/dns.ts" for import "default"

      .wrangler/tmp/pages-QRbsC1/chunks/index_BiYVbPG6.mjs:11:7:
        11 │ import require$$0$5 from 'dns';

  ✘ [ERROR] No matching export in
  "node_modules/cf-mongodb-polyfills/src/dns.ts" for import "default"

      .wrangler/tmp/pages-QRbsC1/chunks/index_BiYVbPG6.mjs:11:7:
        11 │ import require$$0$5 from 'dns';

its very specific but thats why im asking if I even need it with pages

Diego•2/28/25, 9:46 PM

Can I get the data Cloudflare provides in Cloudflare Web Analytics for a Pages site without custom domain with the GraphQL Analytics API or another API?

Hamidzadeh•2/28/25, 11:24 PM

hey guys.. I have a rather dumb question.. is it possible to define a Scheduled Handler on nextjs deployed on Cloudflare workers (using open next)?

jumpspace•3/1/25, 2:43 AM

gm. I am creating a websocket worker in honojs without durable objects. does anyone have any idea on how much will i be charged if I keep the connection open for 24*7

sathoro•3/1/25, 3:27 PM

You are using Node.js 18.17.1. For Next.js, Node.js version "^18.18.0 || ^19.8.0 || >= 20.0.0" is required.

You are using Node.js 18.17.1. For Next.js, Node.js version "^18.18.0 || ^19.8.0 || >= 20.0.0" is required.

this is on a new next-on-pages project. it seems to be ignoring my NODE_VERSION environment variable

sathoro•3/1/25, 3:35 PM

ok so unlike what the README says, you actually have to add a .nvmrc file

James•3/1/25, 3:42 PM

NODE_VERSION

NODE_VERSION

should work fine - you'll need to set it on both preview and production environments though

JJames `NODE_VERSION` should work fine - you'll need to set it on both preview and prod...

sathoro•3/1/25, 3:47 PM

I was pushing to production and the node version was showing under the build settings

sathoro•3/1/25, 3:56 PM

for fun, I added it to the preview environment and deleted the .nvmrc file and it did not work

robmarscher•3/1/25, 5:39 PM

I was trying to migrate from Cloudflare Pages to Cloudflare Workers with Static Assets and found that I was unable to use Cache Rules the same way. I opened an issue in the documentation repo - https://github.com/cloudflare/cloudflare-docs/issues/20445

Walshy•3/1/25, 5:47 PM

the reasoning behind that is complicated

Walshy•3/1/25, 5:47 PM

working on a doc for cache.

Walshy•3/1/25, 5:48 PM

but Assets already caches

Walshy•3/1/25, 5:48 PM

so there's no need for your own cache above

BestSpyBoy•3/1/25, 7:50 PM

i love cloudflare pages but man what is this

BestSpyBoy•3/1/25, 7:50 PM

half joking the dns verification is usually very quick :)

WWalshy so there's no need for your own cache above

robmarscher•3/1/25, 9:34 PM

Thank you so much for the quick reply. For SWR content sites, it’s really useful to be able to return cache headers from the worker and then have that intercepted by the edge cache without ever invoking the worker on subsequent requests. It’s my understanding that isn’t possible with Cloudflare Workers.

Walshy•3/2/25, 3:33 AM

Was just reading up on Waku and the related issues that prompted this. Definitely needs more discussion and thinking our side, hoping my doc gets everyone aligned on state today and helps figure out future path

you're right it's not gonna work today - thanks for bringing this up!

matt•3/2/25, 4:14 AM

yikes... i think i just signed up for a year of Pro thinking it was the same thing as Workers Paid :\

matt•3/2/25, 4:16 AM

well played, cloudflare

sathoro•3/2/25, 4:23 AM

lol

g6•3/2/25, 6:50 AM

are there still plans to support inbound UDP connections?

1984 Ford Laser•3/2/25, 9:52 AM

Will the new Images binding be updated to allow more than 10 transforms per source image, or should I use the Quota Increase form to request a higher limit?

sdr•3/2/25, 9:48 PM

Im getting some strange behaviour in prod when my worker's fetch to googleapis is hanging / timing out.
When I run request via curl with the same params, the request succeeds. Am I missing something obvious?
Im not using the google node library, Im just making a standard HTTP request.

Everything works ok in dev so Im trying to figure out what about the prod worker doesnt work right.

curl -X POST \
 -H "Content-Type: application/x-www-form-urlencoded" \
 --data-urlencode "client_id={GOOGLE_OAUTH_CLIENT_ID}" \
 --data-urlencode "client_secret={GOOGLE_OAUTH_SECRET}" \
 --data-urlencode "refresh_token={USER_REFRESH_TOKEN}" \
 --data-urlencode "grant_type=refresh_token" \
 "https://oauth2.googleapis.com/token"

curl -X POST \
 -H "Content-Type: application/x-www-form-urlencoded" \
 --data-urlencode "client_id={GOOGLE_OAUTH_CLIENT_ID}" \
 --data-urlencode "client_secret={GOOGLE_OAUTH_SECRET}" \
 --data-urlencode "refresh_token={USER_REFRESH_TOKEN}" \
 --data-urlencode "grant_type=refresh_token" \
 "https://oauth2.googleapis.com/token"

matt•3/3/25, 2:00 AM

do worker -> tunnel connections work for non-http? eg. postgres

Mmatt do worker -> tunnel connections work for non-http? eg. postgres

Cyb3r-Jak3•3/3/25, 2:17 AM

You can do it with Hyperdrive
https://developers.cloudflare.com/hyperdrive/configuration/connect-to-private-database/

Cloudflare Docs

Connect to a private database using Tunnel · Hyperdrive

Hyperdrive can securely connect to your private databases using Cloudflare Tunnel and Cloudflare Access.

CCyb3r-Jak3 You can do it with Hyperdrive https://developers.cloudflare.com/hyperdrive/confi...

matt•3/3/25, 2:32 AM

thanks cyber, I played around with that yesterday but i've implemented multi-tenancy in my DB using a schema+role per-tenant... and since those are included in the hyperdrive config, i'd quickly breach the limits for number of configs allowed per account

im still researching but hyperdrive seems like the best option, if i do go ahead with it i'll have to switch back to a single schema with row-level security and update drizzle to apply RLS in migrations & then also ensure every transaction sets local settings to apply the auth

matt•3/3/25, 2:34 AM

im also doing per-tenant worker script deploys so its a shame that if i did move to hyperdrive, every worker would technically have access to the full db -- previously I had a nice setup where i provisioned the worker with just the schema name + user/pass needed to access its own data

ideally i'd switch to hainvg a D1 db per worker, but I need GIN indexes for fast filtering on a Record<string, string> column where the keys are not known ahead of time

Kiran•3/3/25, 7:15 AM

has anyone here gotten sequelize to work on cloudflare workers? For me it just indefinitely hangs in the new Sequelize() method without any errors

Silvan•3/3/25, 11:02 AM

Do i understand correctly that the caches api overwrites the response with the data in the cache if its a hit?
In metaframeworks you often have a load function that runs before your page renders. i tried it there and on cache hit i only get my cache data back (not the website) even without writing New Response..

Just making sure that i have to extract the logic i want to cache inside an api route

Erisa•3/3/25, 11:29 AM

await cache.match(request)

await cache.match(request)

returns a

Response

Response

on cache hit, what you do with that response is up to you and your code

Silvan•3/3/25, 1:10 PM

Hm in that case i should try again. Also weirdly enough when i check on github i also see some people do

platform.env.CACHES

platform.env.CACHES

instead of just

caches

caches

(with sveltekit) those should both be the same right?

Silvan•3/3/25, 1:11 PM

in my head the env is for bindings so its weird to see

Erisa•3/3/25, 1:29 PM

i think (but could be wrong) thats just the way svelte chooses to expose it

Silvan•3/3/25, 2:07 PM

Yea both work but platform is easier to type. even tho i still have the same issue but im assuming this is a sveltekit issue im having here

SSilvan Yea both work but platform is easier to type. even tho i still have the same iss...

Hello, I’m Allie!•3/3/25, 2:11 PM

Just to confirm, you are doing

platform.caches

platform.caches

, not

platform.env.CACHES

platform.env.CACHES

, right?

HHello, I’m Allie!Just to confirm, you are doing `platform.caches`, not `platform.env.CACHES`, rig...

Silvan•3/3/25, 2:12 PM

yes i missed a column i indeed use platform.caches

Sam•3/3/25, 2:35 PM

Best place to post workers build issues is in #workers-help ? or somewhere else, I also have enterprise plan if I should post it in a ticket somewhere?

Silvan•3/3/25, 3:35 PM

Has anyone found a nice solution on typing

Response

Response

in frameworks? sveltekit and cf

Response

Response

types work interchangeably but typescript isnt very happy (as Response dosent do it either)

captain•3/3/25, 4:14 PM

hey everybody...getting a little frustrated not getting the functions folder in my svelte pages project to be recognized by wrangler and upload...seems so basic. It's at the top level, i used the cloudflare create to start the project, haven't done anything too fancy. the pages project loads and shows pages but the functions folder (and a basic script to show its working) is just not being uploaded and in the console when deploying it doesn't show being uploaded. Any ideas or some small thing I am not doing that I a missing? banged my head on this for hours, employed the help of grok 3...no go. Thank you to anybody that might know or might be aware of some flaw. Latest version of wrangler being used. New project that was created yesterday.

captain•3/3/25, 4:20 PM

and now..with fog clearning..i see this:

https://developers.cloudflare.com/pages/framework-guides/deploy-a-svelte-kit-site/#functions-setup

So i am guessing this has something to do with it...

Cloudflare Docs

SvelteKit · Cloudflare Pages docs

Svelte is an increasingly popular, open-source framework for building user interfaces and web applications. Unlike most frameworks, Svelte is primarily a compiler that converts your component code into efficient JavaScript that surgically updates the DOM when your application state changes.

Silvan•3/3/25, 4:27 PM

Functions contained in the /functions directory at the project's root will not be included in the deployment

Functions contained in the /functions directory at the project's root will not be included in the deployment

Silvan•3/3/25, 4:28 PM

whats stopping you from writing +server.ts endpoints?

SSilvan ``Functions contained in the /functions directory at the project's root will not...

captain•3/3/25, 4:30 PM

just learning that now, i (and all the AI's) were under the impression it followed the pattern of the functions folder set up. Nothing is stopping me, just new to pages and wasn't aware as this is the first mention of this difference on that link. searching the internet everywhere else I couldn't find that note.

Silvan•3/3/25, 4:31 PM

Pages is a bit a hacky concept imo. Maybe why this exists now https://developers.cloudflare.com/workers/frameworks/framework-guides/svelte/

Cloudflare Docs

Svelte · Cloudflare Workers docs

Create a Svelte application and deploy it to Cloudflare Workers with Workers Assets.

captain•3/3/25, 4:34 PM

yeah that's where i found it. In my sunday experiment i had set up svelte pages without functions and then created a worker backend. But i was running in to CORS errors over and over again, so i thought maybe just using the functions feature (that i thought was available consistently on all pages frameworks) would be the way to go which then...destroyed me sunday

Silvan•3/3/25, 4:35 PM

cloudflare is very different to many other services i agree its a hard learning curve at the start

captain•3/3/25, 4:36 PM

but the irony is 2 minutes after i posted the question, i found that link. But still...it should be more front and center and wrangle IMHO should perhaps have a console error that says "we noticed a functions folder, please note svelte wont recognize this folder and yo must do it like ...., please refer to this example...."

✘ [ERROR] No matching export in "node_modules/cf-mongodb-polyfills/src/dns.ts" for import "default" .wrangler/tmp/pages-QRbsC1/chunks/index_BiYVbPG6.mjs:11:7: 11 │ import require$$0$5 from 'dns';

curl -X POST \ -H "Content-Type: application/x-www-form-urlencoded" \ --data-urlencode "client_id={GOOGLE_OAUTH_CLIENT_ID}" \ --data-urlencode "client_secret={GOOGLE_OAUTH_SECRET}" \ --data-urlencode "refresh_token={USER_REFRESH_TOKEN}" \ --data-urlencode "grant_type=refresh_token" \ "https://oauth2.googleapis.com/token"

The /dist is for your static assets, the /functions folder is for your Pages function (https://devel

Similar Threads

Similar Threads

Similar Threads