Yeah, the

_worker.js

will run on any request, with the idea being that you add your own routing or custom logic instead of relying on the built-in one

does

_worker.js

override all requests? aka how does one serve static assets from Pages?

I saw the

return env.ASSETS.fetch(request)

snippet on the docs page, is

ASSETS

a special

env

pass-through to the static assets?

> Then call env.ASSETS when you want to serve static assets. from another line, so I guess that's true 🤔

yep

env.ASSETS.fetch

is the way to go

I see in the docs, from the

context

object https://developers.cloudflare.com/pages/platform/functions#writing-your-first-function

env, // same as existing Worker API

but I'm having a hard time finding where

env

is documented in the Worker API

a cross-link in the Pages Functions docs would be helpful, searching for "env" is a bit too wide to be helpful 😅

I guess I found it in the new module syntax https://developers.cloudflare.com/workers/runtime-apis/fetch-event#syntax-module-worker

but where is

ASSETS

coming from? something special to Pages?

Yep, it's a thing set by Pages for fetching your assets

The Pages docs are the best reference for how to use things like

env

The syntax differs slightly from normal Workers

right, I was pointing out that the only place

env

is "documented" is in the "Writing your first function" code snippet, where the comment says it's "same as existing Worker API"

(also, there's no cross-link to "existing Worker API" for

env

, and I can't find where it's mentioned, so effectively

env

is entirely undocumented at this point)

In most cases in Workers,

env

basically has

type: any

, as the structure of

env

is defined by the User. The only time(that I can think of off the top of my head), where

env

has a predefined child is in Pages, as you mentioned, with

env.ASSETS

.

Hello 👋 I'm trying to use twilio inside of a cf function. Unfortunately, their node sdk uses common js. When building, Im getting errors like

Could not resolve "fs" (use "platform: 'node'" when building for node)

. I tried playing with the default webpack config, but couldnt get it to work. Do you have any hints, on how to solve this issue?

The issue there is that the Twilio SDK relies on access to the file system, which Workers does not have

When that came up in the internal chat today, @threepointone said “.. and we can’t polyfill that until R2 is available..” and everyone else in chat went: 👀

In this specific case, we could probably polyfill it with stubs, and just not call functions that require a file system

Do you have a sample snippet of how you’re using it?

yes, thank you very much for your help 🙏. Im just trying to generate access tokens for a user to join a video chat. https://gist.github.com/mabey01/fba5fa900b838a6e1d094fafa407d909

the filesystem access is also a problem, but i couldnt even get it to build. It was complaining about all the require statements not being able to resolve 🤔

I'm in the middle of trying to do something similar, but with the Stripe SDK if the thing you're doing doesn't actually use the fs/etc, you might be able to use a webpack config like they're doing in this Stripe+Cloudflare demo https://github.com/stripe-samples/stripe-node-cloudflare-worker-template with the resolve.fallback properties unfortunately that means you need a custom webpack config, which Pages doesn't support, so you have to have a build step to build the route you want

aka if you want

/functions/api/messages/send.js

than you'd need something like

/src/send-message.js

and have Webpack build the output to

/functions/api/messages/send.js

as part of the build, then Pages will deploy your built script

it's not a great DX at all, but in theory it should work (I'm still in the process of getting Stripe to work, so...)

Did you ever check this out? I am in the process of working on something on Pages and Stripe is going to be a huge part of that soon. So Im gonna be headed down the same road as you shortly. I saw this before your posts and now I am wondering what this announcement means if you are having so many issues. https://blog.cloudflare.com/announcing-stripe-support-in-workers/

I didn't see that earlier, it would have started me in a much better place

that blog post feels very disingenuous to me: the Stripe SDK isn't "native" in Cloudflare at all, you have to use polyfills to make it work

if you use Webpack you have to polyfill all this junk for it to even build https://github.com/stripe-samples/stripe-node-cloudflare-worker-template/blob/master/webpack.config.js