John Royal

@_ashleypeacock Access for the @alchemy_run team when? Would love to support this on day 1 if possible!

This is how easy it's going to be to send emails on Cloudflare when Email Sending becomes generally available, it couldn't be simpler: 1. Onboard your domain, effectively two clicks in the dashboard 2. Add the email binding to Wrangler config 3. Send emails using the code below

@samgoodwin89 100% - was thinking that Cloudflare static assets for frontend + Lambda/EC2/etc backend for anything that requires real Node would be cool to try. CloudFront is PAINFULLY slow to update and Alchemy-effect’s abstractions should make this possible.

I think I’m convinced that CloudFront is a non starter. Even if you want to use AWS, you should still use Cloudflare for hosting the frontend.

If your codebase is a mess because of AI, you're doing it wrong. I always had a list of refactors I wish I could do if I had the time. Now you can fix one file and let a model apply your pattern to the rest. No one has time to follow their own principles perfectly, but LLMs do.

Is decoupling Workers from bindings actually in the cards? Would help with platform lock-in and onboarding new devs and I think it's possible to some extent since many bindings are just JS wrappers for HTTP APIs. But I know bindings are integral to how the runtime works and enable a lot of Workers magic (e.g. DOs, RPC calls). Is there a way to preserve those benefits while being able to run something resembling a garden variety Node app?

@joeychilson Heard and planned

This means I can finally delete this script I've been using for months

Alchemy now has its own Vite plugin to streamline local development. No more .dev.vars or vite.config.ts boilerplate - control everything from your @alchemy_run code. Manage Secrets and Env variables however you want. Blog post in reply: