Robin van Wijngaarden

@Quintin24 Je begrijpt dat Samsom niet over de vulgraden gaat? Hij is (1) toezichthouder bij Gasunie (geen bestuurder), (2) ze adviseren de minister nota bene zelf om een hogere vulgraad aan te houden, en (3) Gasunie vult geen opslag; dat doen marktpartijen binnen regels van de overheid.

Dit verklaart een hoop gasunie.nl/nieuws/diederi…

@jarredsumner can you run code review against my PR github.com/oven-sh/bun/pu…? 🥹

What’s especially interesting: it catches different bugs. Other code review products tend to be better at surface-level stylistic issues like “filename doesn’t match the project conventions” Claude Code Review regularly catches bugs that only surface from reading tons of code

Been using this in Bun’s repo for weeks & giving lots of feedback This, imo, is the best product in the code review category today. It regularly catches extremely subtle bugs and rarely makes mistakes

@jarredsumner Issue: github.com/oven-sh/bun/is… Possible fix: github.com/oven-sh/bun/pu…

if you have a bun GitHub issue open for awhile with a clear reproduction, reply with a link below & I will have Claude try to fix it today

@jarredsumner Hi Jarred, to support @testcontainers with Bun, could you run the test suite on my PR github.com/oven-sh/bun/pu… or throw Robobun against the original issue?

@cnakazawa @colinhacks wrote similarly about this in 2024: x.com/colinhacks/sta… I haven’t found a better answer until this day.

How do you set up monorepos and keep TypeScript fast, without requiring local builds all the time? I'm very confused! Let's say you are building a monorepo with multiple packages, and an example app within the monorepo that consumes the packages. The packages have a build step for publishing, and each package defines their `exports` in package.json. I see these options: 1. Do nothing. Just `tsdown` to build packages and d.ts files on every change. This is simple, but slow for development. `--watch` could work, but I've run into issues doing `pnpm -r build --watch` where it was only rebuilding a subset of packages each time. I'd much rather just have my devserver take care of this for me than running yet another tool locally. 2. Use a "development" condition for source files, and set Vite and TypeScript to resolve "development" in dev. This way you don't need to build during dev, but you also need to ship the source files to npm, otherwise tooling will fail looking up "development" conditions pointing to missing files in production. 3. Use resolver aliases for each tool: Similar to the development condition, without the production downside, but somewhat annoying to manage a list of aliases for each tool. In my experience, when using aliases heavily, there will always be tooling problems since they don't all support aliases, or have different config etc. I guess Vite 8's tsconfig support simplifies this a bit, but that's opt-in for now. For all three, TypeScript checks something different. In some versions it checks the source, and the compiled output in others. If you only check the source, you can't guarantee that the published package's types will be correct. Nothing will stop you from publishing packages with missing types, unless you set up yet another CI job to check for this specifically. If you only check the compiled output, you have to build it all the time during development. How do you handle this for a repo where some packages are published and some are not? Yet another solution could be to compile a project into `src` for publishing as well, so that `exports` are the same for development and published packages. That way no special config is needed. It requires a bit of custom setup for publishing, though. Examples: * fbtee.dev at github.com/nkzw-tech/fbtee currently requires `pnpm build` each time a package is changed. * fate.technology at github.com/nkzw-tech/fate currently uses aliases for Vite, but requires a `pnpm build` for TypeScript when the public interface of a package changes. * Athena Crisis at github.com/nkzw-tech/athe… just uses everything from source as the packages are not published to npm. However, inevitably, with any of the three solutions, tools will become slow as the repo grows. Now what do you do? `isolatedDeclarations` + checking in d.ts files for each repo? A `tsconfig` for each package, which makes everything even slower since TypeScript will now do overlapping typechecks across your project? Then paper over with Turborepo to make it feel ok? I think Project References in TypeScript are supposed to be the solution, but somehow that hasn't worked well for me and hasn't sped up TypeScript that much. What do you do? What do you suggest? What am I missing?

@worm_emoji @jarredsumner node:util styleText covers the basics of chalk: pawelgrzybek.com/node-js-added-…

@jarredsumner chalk

What else should we add to this list?

@itskritix @bunjavascript @cirospaciari x.com/alistaiir/stat…

@bunjavascript @cirospaciari When postgresql?

In the next version of Bun Bun.SQL's builtin MySQL adapter gets 16% faster compared to Bun v1.2.21

We're Still Underestimating What AI Really Means: tinyclouds.org/underestimatin…

Ouch, looks like a big Google Cloud outage. Good luck for the engineers in the war-room.

@AlexanderNL In NL heb je ook live verkeerslichten data (nederlanddigitaal.nl/initiatieven/p…). Onder andere Flitsmeister heeft dat geïntegreerd. Bij ons telt het alleen niet af, want bij ons is het dynamisch door de lussen in de weg.

in china leven ze in de toekomst hoor

@wspruijt I’m also wondering that. I’m using ChatGPT at least twice as much than Google nowadays.

At which point will Google go 100% Gemini on Google Search? If they don’t it’s a matter of time until ChatGPT surpasses them. Probably not any time soon because of ad revenues 🤷‍♂️

@rickpastoor :(

That's it then. The official final day for Rise.

@krijnrijshouwer 🔥

Meet @Lemni. Set up custom Ai agents for all your customer interactions, in just minutes. So every interaction stays personal—no matter how big you grow. Try our Beta → lemni.com

@joost_akker @NextDNS yes!

Any followers who use @NextDNS and would like to test an iOS app in progress? 🙂

lol, wanted to google process.env.CI but apparently it's a valid URL and ended up there

@bunjavascript @jarredsumner The blog post is wrong. It’s the other way around. :)

Bun v.1.2.1 - Fixes 32 bugs - S3Client gets `storageClass` support - X25519 support in node:crypto - Node.js compatibility improvements for node:fs & node:child_process. fs.stat uses less memory. - Several memory leak fixes Thanks to 16 contributors! bun.sh/blog/bun-v1.2.1

@JeanPaulH Tijd vliegt. Geniet van de welverdiende rust! :)

Een bitterzoet afscheid, maar we zijn dankbaar voor alle mooie jaren.

@colinhacks that’s really cool :)

Devin implemented this PR for JWT validation in Zod x.com/cognition_labs…

I was hoping GitHub would announce Claude support today and they did 🙏

someone even made a timeline bullenweg.com