Leonardo Dominguez

@alistaiir @bunjavascript How would you remove it on this case?

In the next version of Bun `Bun.cron()` accepts a callback for recurring in-process tasks

Since it's clear you guys love free stuff... We have a small arsenal of stuff related to a certain Sentry product to give away 👀 To win, you must: - follow @sentry - retweet this post - reply with the answer to this riddle: I’m an AI-powered code psychic, here to warn you about the bugs in your future. Looks like I'm too late to warn you about that gas station sushi you had for lunch. Who am I? We'll pick random winners from the pool at the end of the week 🫡

@sentry Sentry Seer

@thdxr yeah, it's very similar to OpenAI image playground

late to this but this t3chat canvas thing for image gen is really good obvious in hindsight now but shoving image gen into chat was weak ux and image gen is specifically a place where i want to try different models so not having to switch tools is great

@WBCBaseball lets goooooo

Fernando Tatis Jr. came up HUGE in yesterday’s game 🇩🇴 Repost and reply for your chance to win a Tatis Jr. Team Dominican Republic jersey!

@devheb @claudeai With that pricing? None.

@claudeai How many startups killed with this one?

Introducing Code Review, a new feature for Claude Code. When a PR opens, Claude dispatches a team of agents to hunt for bugs.

@aarondfrancis @joelhooks If you are looking for inspiration, imo worktrunk.dev is the best tool to manage and use worktrees, it just work.

@joelhooks Right, agreed! I'm asking because I'm building a tool (soloterm.com) that will manage it for the human. So I'm purely interested in the technical stuff.

Why do people like git worktrees over discrete checkouts? (This isn't bait, it's research)

@aye_aye_kaplan Genuinely curious, why go with Postgres if you’re already using MySQL for everything else?

Story time! The very first version of Bugbot we launched was stateless. We kept track of runs in our analytics database and we only used that data offline for metrics. Whenever we needed to analyze run metadata, we had to do online lookups from the database. Relying on our analytics database during online operations was definitely tech debt. We were using a large RDS cluster that was already running hot from offline usage. We started noticing that some Bugbot runs were failing because of external analytics load; by that time, we had added a few Bugbot-specific tables to it, so we had to come up with a migration plan quickly before this became a widespread availability issue. We chose PlanetScale Postgres for our new Bugbot cluster. We already had many terabytes of data in PlanetScale MySQL/Vitess which was working incredibly well, so we felt comfortable with this choice. The migration went very smoothly, and now all of Bugbot's queries are instant and we stopped worrying about downtime!

@dcarter_js lfgggggg

chat sdk adapter for durable objects github.com/dcartertwo/cha…

@Baconbrix @0xPleb0 That won’t work for opening a modal on top of the tabs, which is a common pattern used by many popular apps

@0xPleb0 Just set a tab role=“search” and set any icon

@Baconbrix wen custom action btn in expo router? 👀

@GustavoValverde ISR/SSG infra, smart routing, edge cache interception, default asset/image/worker setup, and sane CDN invalidation. If you want to keep reading: opennext.js.org/aws/inner_work…

@Foocux Wait, what are you referring to as full-featured Next.js? Full featured Next.js is not a full featured Vercel.

I honestly don't understand the vendor lock-in people state about Next.js What does that even mean? 98% (50+) of the Next.js I've deployed are outside of Vercel.

@GustavoValverde If other providers can’t replicate the custom infra needed for full-featured Next.js, that is vendor lock-in. No other framework requires this level of provider-specific setup.

@Foocux They have custom infrastructure and integrations with their main partner (AWS); we don't 😅 Next.js will work better in Vercel because they're the ones building it (and the main customer), but that's not to say it doesn't work in outside Vercel...it does.

@GustavoValverde I get the point, but the fact that the creators run it on Lambdas makes it hard to argue that’s not the right place for it.

This is a question that I've made before several times to my clients: Why would you even run Next.js in AWS Lambda? That's not a good use case (nor framework) for Lambdas. I ran through that issue myself (through one of my clients), and they fixed it months after. But the actual thing is that Lambdas are not for everything, and certainly there are better ways to deploy Next.js, Nest.js and similar frameworks in AWS (it's commonly more expensive in Lambda).

@GustavoValverde Lots of issues out there, X and the OpenNext FAQ are full of them. Sure, maybe it works for you in a container (not sure if fully featured), but it’s ironic that Vercel can run Next on AWS Lambdas flawlessly while others can’t. Kinda says everything.

@Foocux I honestly never had the need to look at OpenNext, and I've deployed Next.js in several ways. I would have to see what's the specific issue that someone has had previously with Next.js in a containerized deployment, or in a Node.js runtime.

@GustavoValverde Sure, in theory you can switch tech. In reality, you often can’t choose the stack and don’t have time to migrate. That’s why so many devs feel locked in with Next, and why OpenNext exists.

@Foocux If I have to run something on AWS Lambda or Cloudflare Workers, I wouldn't use Next.js. Most use cases for those platforms have better frameworks (Vite, Hono, etc) 😅

@psincraian @GustavoValverde re: restricted on features Vercel own infra runs on lambda so I don’t think that’s the reason why it doesn’t work :)

@Foocux @GustavoValverde I have deployed it in my own server using their docker image example. Of course if you want to deploy it on Lamba or Workers you will face limitations because those are restricted on features

@skeptrune @RhysSullivan Link to the guide 👀

@RhysSullivan this just made my day

i can't stop thinking about this. i really don't think the sandbox direction for programming makes sense

@nestframework esm + vitest is hugeeeee, can't wait for it!

🚀 Big updates coming in NestJS v12: ✨ Native ESM support ⚡ Faster testing with Vitest + SWC (default for ESM projects) 🧩 Standard Schema in route decorators - use Zod, Valibot, ArkType, and more 🎨 A complete redesign of the NestJS websites Details: github.com/nestjs/nest/pu…