Jon Mumm

@dcarter_js @dillon_mulroy @zerocipherz d1 databases too... only reason i use Neon

@dillon_mulroy @zerocipherz very interesting 👀

Why can't we deploy workers per branch and get a preview URL easily, similar to pages? I would love this feature. Right now i have to deploy separate workers to make this tenable so i can have proper environments. Am i doing something wrong? i could never get deploy previews working on 1 worker in the way I expect it to work. If we could connect the worker to multiple branches and get truly separate environments, that would increase DX drastically i think. cc: @dillon_mulroy @CloudflareDev

@ctatedev How about Apple Auth?

New: Programmatic API for 𝚎𝚖𝚞𝚕𝚊𝚝𝚎 Automated test suites + local emulators: 1. Create emulator (Vercel, GitHub, Google) 2. Set env var (and/or pass to SDK) 3. Reset data and close when appropriate

@miacmal @Cloudflare Can we get Workflow bindings in getPlatformProxy?

hi everyone!👋 excited to share that i'm now working on @cloudflare workflows & queues! also... testing workflows locally just got better: you can now mock steps, simulate events, & inspect what's happening at each stage 🔍 if you have any feedback, please reach out!

@DavidKPiano Would the schemas be accessible on the actor?

API design q: if we were to add schema (e.g. Zod) support to the next version of XState, should it be nested under one `schemas` property or separate properties? Or something else? Open to ideas

@lgrammel agent as a class name is overloaded, but do like an object to be able to pass around and mock methods on

Which version do you prefer and why? (poll in reply)

@NathanFlurry When you are at scale, you usually know what your product is, and what data needs to be joined—day 1 you don't know that yet. Some model that replicates actors/shards to an OLAP database might be a nice balance—but two databases is more complicated than one.

good point! for apps at scale, actors make you think the same way you would with cassandra/dynamodb/etc but with a lot more flexibility. it's interesting to take this to smaller use cases and overcome the joining challenge. i want to experiment more with some variation of "materialized views" of data from other actors, but i need to gather a larger dataset of use cases + how that'd map to actors. plus figure out how to make it "just work" without extra cognitive load.

Been toying with Rivet Actors compares up against popular BaaS However – Rivet Actors is a bit more of a "serious" tool based on arch that scaled WhatsApp, LinkedIn, Cloudflare, etc. What do you evaluate when looking at tools beyond the vanilla DB?

@BraydenWilmoth This is a much better abstraction and name than “Durable Objects”!

Today we're announcing the all new @cloudflare/actors library to help make developing with Durable Objects easier than ever before. Powerful feature defaults, improved interfaces, and a new default export handler. So what all can it do today? - Get current instance by name - Store all instances by name and last accessed - Route to a DO without a user-defined Worker - Define instance name within a DO - Execute SQL with template literals - Run SQL Migrations - Set multiple alarms by date, delay, or cron - Access an Actor by class (not by env.XY) - Destroy instances How to use it: `npm i @cloudflare/actors` Examples: ----------- Basic Worker ^ and yep. that's the whole index.ts file you need for the most basic Worker now. RPC into an Actor: ^ now you can just do a `.get` on your Actor class directly and pass in the instance name to interact with it via RPC. No more creating a stub and doing the things. Alarms: ^ schedule as many alarms as you want and define them with a Date, seconds delay (see above), or cron and pass in an array of parameters that map to the function you're calling into. Shout out to @threepointone for his work here. Storage: ^ define & run migrations, query with `this.sql` template literals. You can also see here how we log out `this.identifier` which logs out the user provided "name" value of the instance (not the ID itself). Also the second param in our `handler` allows us to define that we should in fact track all instances we create by name and store it in another instance altogether to keep track of. Shout out to @LambrosPetrou for his migrations work! Handler: As shown in all the examples above you can use our new `export default handler(...)` to export a Worker or an Actor. This handler does a lot of the magic of some of the features (such as tracking instances, holding identifiers and more). Best of all, these features can be used by your DurableObject classes as they are today without extending Actor... ...or.... you can just extend "Actor" instead of "DurableObject" and get all of the power this library unlocks automagically. ---- This is a BETA release to get user feedback. Intention of this library is to make working with various components of Durable Objects much easier, have less overhead, and add things here that may be more difficult or time consuming to add to the runtime to provide benefits to developers fast. Please provide feedback & share what types of features you would love to see in this library. Hope you all enjoy it!

@kathyyliao Would love to see chrome.tabCapture on this list to be able to publish webrtc streams from a worker through puppeteer

Generate pdfs, take screenshots, grab markdown + more. Just one api call away. Let me know what actions you’d like to see next~

@zplesiv @NathanFlurry This

Today's struggle: CF's Durable Object WebSocket fetch handler can't be used if you need auth. Query params are insecure, so RivetKit needs to listen for a handshake msg on the edge worker before opening a proxy WS to the DO.

@dok2001 @Cloudflare github.com/actor-kit/acto…

What are you building on @Cloudflare Workers Platform? Best replies get swag sent to them!

@BraydenWilmoth @moesmufti Finally! x.com/jonmumm/status…

@moesmufti yeah... work needs done on the lower level to improve this. I think ideal world a constructor could just take whatever params a user wants to define. but for now I should at least alias "DurableObjectState" to "ActorState"

In a world..... where this is the minimum it took to define a Durable Object.... Coming soon to an IDE near you. No worker. Just a class. Export through a handler to route traffic to it.

@ryolu_ Task management

send us your wishlist will try to make them happen 🎁

@NathanFlurry @ActorCore_org Are you trying to lean in to CloudFlare or build the abstraction around it to avoid lock-in? Unclear

Need feedback from Cloudflare Durable Objects/PartyKit/Agents devs: I keep getting people DMing along the lines of "@ActorCore_org is so much easier to use than Durable Objects", but I don't know how to best refine this message. How would you phrase it?

@iamsahaj_xyz github.com/honojs/honox

if you have a Vite SPA and you want to build a backend now but don't want to use nextjs - what are your options? - needs SSR/SSG - should work with cf workers - minimal framework magic - good DX opinions on hono / tanstack-start? asking for a friend 👀

@boristane @basebrainhq @CloudflareDev @DrizzleORM This is beautiful, I only wish they were called actors instead of durable objects, to not confuse them with simple document storage

I keep reading that durable objects are hard let's change that narrative here's how I'm building @basebrainhq entirely on @CloudflareDev I create a new database for every user using durable objects and everything is working with @DrizzleORM boristane.com/blog/durable-o…

@feedthejim @threepointone How closely would that heavy rewrite resemble Vite?

@threepointone first milestone for us is the build part, however we discussed the dev scenario with Igor from your team and I’d love for us to do this. I think this would require a fairly heavy rewrite to abstract the runtimes parts of the compilation

I was waiting until we got something concrete to announce but yolo: we are actively working with the folks from OpenNext and other partners to ship an official build adapter API for Next.js and make it easier to for anyone to support deploying Next.js’ more advanced capabilities.

@BraydenWilmoth @rauchg @pk_iv @eastdakota @supabase Had your emergency response been more accurate and helpful, maybe that wouldn't have had to happen x.com/JavaSquip/stat…

@rauchg @pk_iv @eastdakota @supabase Wasn’t this all because Cloudflare was trying to fix a bug your team helped introduce? 😂

Save money, get better performance, and work with a company that actually cares about security. #nobrainer

@zeeg @Vercantez "As you are implementing, add tests, then run them as you go. Here is the command: ___. Also do run typechecking and linting too"

@Vercantez How do you instruct in how and when to run tests? Obviously there's .cursorrules but I'm guessing I need to feed the agent a tool via an MCP or something?

Can you get Cursor's composer workflow to run things like tests (targetted preferably) today? I'd love for it to run a real validation run after its fixed fast-errors like lint/tsc

@thekitze easy to solve for if you follow TDD

vibe coding a game for 15 mins made me realize that I never liked reckless vibe coding vc means you press accept all and you don't understand the code at all, if it works it works, yolo. I don't like that llms are *not* in a state right now to let them do that. you will pile tech debt and eventually your requests will stop working because everything is a mess