I'm just playing with Pages functions, and getting this error: Compiling worker to "/opt/pages/functions/user-worker.js" > ../../buildhome/repo/node_modules/handlebars/lib/index.js:17:19: error: Could not resolve "fs" (use "platform: 'node'" when building for node) 17 │ var fs = require('fs'); ╵ ~~~~ That "platform" setting sounds like it's for esbuild? Is there a way to set this?

I might look into bundling my function using esbuild during my build phase...

Workers don’t support NodeJS, but only JavaScript (+assorted extra libraries). So you can import things like fs.

^ Erwin means you can't import

fs

he just needs some sleep

Hehe.. no that wasn't it. Turns out I didn't press enter on the second message 😄

Is it possible to connect and create queries with mongoDB Atlas clusters using serverless function?

Yes: https://blog.cloudflare.com/workers-adds-support-for-two-modern-data-platforms-mongodb-atlas-and-prisma/

Thanks, is there maybe a example code?

Yup. Linked in that post: https://www.mongodb.com/developer/how-to/cloudflare-worker-rest-api-realm

Are the "assorted extra libraries" listed somewhere?

probably been asked loads before, but are you able to see logs for pages functions?

Not possible in the beta right now, unfortunately. Your best bet right now is either local development with

wrangler pages dev

or to try/catch and throw errors to a service like Sentry.

thought so, cheers for the response - managed to catch this one by eye (was passing a null value to cookie.parse) but will do that if i run into more issues :))

How does this work with Gatsby? Cannot get it working..

is there a specific wrangler version i need for this? on the latest stable version (npm)

pages

isn't a valid subcommand

Yeah you need the new Wrangler 2 beta https://blog.cloudflare.com/wrangler-v2-beta/

npm install wrangler@beta

cheers

oof

Yeah you're doing a unicode there with the backslash u.

\u200B

for example is zero-width-space

@User The alpha is working great by the way

Wonderful to hear!

And once you exclude the functions folder you can rebuild in seconds

I would definitely make a documentation page that explains the benefit of doing that by the way

I was looking at caching yesteday, and realized that we're not sending the same cache-control headers that you'd get in production. Anyone have any thoughts on whether they want here?

My concern about attaching big ol' cache headers on the static assets locally is that it your browser cache might be a bit too aggressive for local development.

But, good to have a proper emulation of production 🙃

I mean I definitely would not want caching

Allowing the option with command line is good, but for most people if you’re testing some thing you don’t want it to cache