Is there a timeline for when it may be made available?

There is not, there's complexity involved because the Functions map to your pages.dev not your custom domain. Your pages.dev zone doesn't have image resizing

ok thanks for the info. I will stick with using plain workers for just the image portion. Was hoping I could align all my code in one deploy flow using pages/functions

Here's what I did: 1) Store my images in R2 2) Make my R2 bucket public but never expose the public URL 3) Have a Functions route for the images :

mydomain.com/profile-photos/ABC123.jpg?width=1024,quality=75

etc 4) In my function for that route, I proxy the request to the public R2 domain to something like:

mydomain.com/cdn-cgi/image/width=1024,quality=75/https://pub-MY_PUBLIC_R2_DOMAIN_HERE.r2.dev/ABC123.jpg

It works great and I get a response:

cf-resized: internal=ok/- q=0 n=280 c=15+87 v=2022.12.7 l=79202

Have you done any analysis on whether you'd save money by also storing the resized images in R2 instead of resizing them on demand?

No, Right now, I'm not expecting enough traffic to even exceed the free limits

Out of curiosity, is this also the reason for complexities around other features like wildcard custom domains not being supported for pages?

Pretty much yep. SSL for SaaS Enterprise is needed for wildcards. The pages.dev zone is the these are added (obviously), that doesn't have SSL for SaaS ENT.

It's on the roadmap to support it regardless. We just need to work with the ssl for SaaS team

Justin that is a very interesting approach. I am trying to determine if it works for my use case. I don't know that is will since I am using some image features that are only available in workers. I am actually layering in 7 different images together to stitch them together with cf images using the

options.cf.image.draw.push({});

option. Like I said I have it working in plain workers at the moment but would love to use functions from a code stand point so I can have it all live with my other functions and deploy it all in the same way.

I'm trying to deploy as instructed here and get this error on deployment, is something broken? https://github.com/cloudflare/next-on-pages

12:50:36.162    Verify run directory
12:50:36.162    Executing user command: npx @cloudflare/next-on-pages
12:50:36.330    /opt/buildhome/repo/node_modules/@cloudflare/next-on-pages/dist/index.js:6013
12:50:36.330                  ({ type, expression }) => type === "ExpressionStatement" && expression?.type === "CallExpression" && expression.callee?.type === "MemberExpression" && expression.callee.object?.type === "AssignmentExpression" && expression.callee.object.left?.object?.name === "self" && expression.callee.object.left.property?.value === "webpackChunk_N_E" && expression.arguments?.[0]?.elements?.[1]?.type === "ObjectExpression"
12:50:36.330                                                                                         ^
12:50:36.331    
12:50:36.332    SyntaxError: Unexpected token '.'
12:50:36.333        at wrapSafe (internal/modules/cjs/loader.js:1054:16)
12:50:36.333        at Module._compile (internal/modules/cjs/loader.js:1102:27)
12:50:36.333        at Object.Module._extensions..js (internal/modules/cjs/loader.js:1158:10)
12:50:36.333        at Module.load (internal/modules/cjs/loader.js:986:32)
12:50:36.333        at Function.Module._load (internal/modules/cjs/loader.js:879:14)
12:50:36.334        at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:71:12)
12:50:36.335        at internal/main/run_main_module.js:17:47
12:50:36.344    Failed: build command exited with code: 1
12:50:37.301    Failed: an internal error occurred

What's your

NODE_VERSION

env var set to? It'll need to be at least

16

I'd also just be a little wary with

next-on-pages

if you run into any issues. Its state of maintenance and support right now is questionable, and I've seen others have more success with Netlify or Vercel for their projects.

Hey, I'm trying the next-on-pages thing as well, with "experimental-edge" runtime. And for me, it seems that routes like "[id].js" are not getting "query" or "params" in the context - is this normal?

That doesn’t sound normal, no. I’d recommend filing an issue on the repo but it might be some time until you hear anything back 🙁

Apparently there is already an issue... https://github.com/cloudflare/next-on-pages/issues/35

That's the iffy thing about next-on-pages, for the other frameworks like remix/sveltekit pages support is maintained primarily by the framework devs alongside the other ecosystems so it's mostly kept up to date, vercel don't have anything to do with this package so it's just cloudflare/community. Hopefully due to how in demand next-on-pages is it'll grow and get strong community support, but if you want to actually use in production at the moment it's likely not the best choice. At least that's my take on things atm, Greg did respond to a bunch of PRs a couple of days ago it is making progress.

I love next as a framework, but I hate the fact that they steer things quite heavily towards Vercel. Every new release breaks everything for other users, making vercel the only option if you want to use the latest and greatest. And it seems even intentional rather than accidental. So for that reason, I will never use Vercel for anything. But yes, hopefully we'll slowly crawl towards more support. At least the next-on-pages stuff is public, unlike the things they do at AWS Amplify to make next work, so it's easier to fix it myself if necessary.

after minor updates to pages project (using astrobuild) started getting an error on every pages that uses functions. The error says

"Error: To use the new ReadableStream() constructor, enable the streams_enable_constructors feature flag."

. Has someone come across similar error? what could be the reason for this error message? I have not change anything substantially in the functions

Thanks, I'm using Node 18. I feel the same though - seems like an intern project and no real effort being put to maintain it. I would have love to have cloudflare host the website given their network PoPs, but you are right choosing Vercel or Netlify might be the more sane thing to do.

how to skip npm installation in cloudflare pages ?

How to deploy functions for static sites?

Give it a try? Or send me a code sample of exactly what you're trying to do and I can try.

tldr: My functions go undetected and paths are giving 404 I have a Hugo site, where I am trying to add functions. I am adding functions/helloworld.js to the public folder and pushing it via wrangler direct upload. For some reason, the

/helloworld

URL gives 404 and even the function itself is undetected in the Cloudflare dashboard even though I can see that the file is uploaded. Am I missing something, should I compile js something like that?

Functions folder shouldn’t be in the public folder

Hey @bkyerv Sounds like your code relies on the Streams constructors flag but your project isn't setup for it - you can change the compatibility date to be more recent or add that individual flag (see the images)

thank you! how are we - users of cloudflare - supposed to be aware of it? in future, is there any way to automatically set the comp date to the latest one? I doubt anyone would opt out of something that may brake production deploy

Automatically using the newest compatibility date would break production - that's why they exist

The only way that you'd need that flag is if your code is depending on behaviour that is behind that flag.

Hey @denniarems if there's no package.json we won't run npm install.