As a very new developer to Cloudflare and web apps in general, I feel like this is a good thing, but I'm not really sure what Pages and Workers are really aiming to do, nor how to decided which features I need. But I appreciate the matrix you're included in responses below.
You can find more info on the blog here blog: blog.cloudflare.com/builder-day-2024-announcements/#static-asset-hosting docs: developers.cloudflare.com/workers/static-assets/ - Confidence
I think it might be possible! People used Pages for next projects in the past. Maybe we won’t get the auto image manipulation because it requires libvips at compilation time, but the other features are feasible
Is this new support more of client side rendering support? Because worker has already support server side rendering like using Hono to send html back via workers?
Update: The binding name is now 'assets'
Example here developers.cloudflare.com/workers/static-assets/binding/#binding
As a very new developer to Cloudflare and web apps in general, I feel like this is a good thing, but I'm not really sure what Pages and Workers are really aiming to do, nor how to decided which features I need. But I appreciate the matrix you're included in responses below.
Neovim! Let's goo!
Is there a blog or documentation link to learn more?
You can find more info on the blog here
blog: blog.cloudflare.com/builder-day-2024-announcements/#static-asset-hosting
docs: developers.cloudflare.com/workers/static-assets/
- Confidence
What about next js?
Exactly; same question!
I think it might be possible! People used Pages for next projects in the past. Maybe we won’t get the auto image manipulation because it requires libvips at compilation time, but the other features are feasible
IIt's all here developers.cloudflare.com/workers/frameworks/framework-guides/nextjs/
- Confidence
So, all next js features are supported now with worker?
@reinhard_silaen Waiting for the reply for the same question too.
Maybe it's time to merge these products? It's becoming a mess 😢
We're certainly making things more streamlined 😄
- Confidence
@@CloudflareDevelopersI don't get it. Isn't pages + pages functions already this idea
Is this new support more of client side rendering support? Because worker has already support server side rendering like using Hono to send html back via workers?
Please make a tutorial using next on pages with cloudflare workers something like a chat app
Sure! Thanks for the feedback
- Confidence
Is there a link to the Github repo that you mention in the demo? It would be nice to see some code.
Sure! Here's the source repo github.com/Rich-Harris/ematchi
- Confidence
How would we bind durable objects?
localy
Same here developers.cloudflare.com/durable-objects/get-started/walkthrough/#5-configure-durable-object-bindings
How about a full stack app with Sveltekit?
Great video, it does look as simple as a Vercel deployment.
How is this different from using pages with worker functions ?
Here's the difference developers.cloudflare.com/workers/static-assets/compatibility-matrix/
- Confidence
So should we use Workers over pages instead now ?
This can help you decide developers.cloudflare.com/workers/static-assets/compatibility-matrix/
- Confidence
Looking forward to mortgaging my house to pay for a DDOS attack on my 3 MAU hobby project.
Need a remix guide fella
Here you go developers.cloudflare.com/workers/static-assets/compatibility-matrix/
- Confidence
@@CloudflareDevelopers 404