With Sandpack 2.0 & Nodebox, we're taking a step forward in improving the development world for students, content creators, open-source maintainers, and more. 🔥 Powerful. Fast. Ready To Use. 🔥

This is so cool!! I absolutely love Sandpack v1 but Sandpack v2 with Nodebox is just... 🤯 Amazing work by everyone at CodeSandbox I can't wait to play with this properly 🎉

Easy to forget, but the debate about signals is the same one we had about 2-way data binding vs unidirectional data flow 10 years ago. Signals are mutable state! They’re bindings with a new name. The simplicity of UI as a function of state is lost when updates flow unpredictably.

Tell me you don't know how to write testable code without telling me you don't know how to write testable code.

We don't talk about this enough...

Joe Previte i would always prefer dependency injection or some other design change to mocking. and probably testing the logic on a higher level (not sure if your example is a simplified version if the real thing)

Everyone sees the missing await / error handling which are trivial to solve. I see the lack of parsing the JSON into something trustworthy via Zod/io-ts. I see so many bugs caused by devs trusting a value provided by the network. Also TS any on .json() aids this problem!

Just use cookies with httpOnly, secure and same-site enabled 🍪 I’ve never understood the fascination of storing tokens in localStorage, especially JWTs they can be stored in a cookie too you know 🤫

Looking forward to the day we as a community realized file system-based routing was a mistake. Once you glimpse over the initial appeal, you see there's a flaw on a flaw. - File names aren't a format dynamic enough to support the extremely dynamic nature of routes; - Concern

Now that React has gone full circle to server-rendered websites like the good old php days... how far away are we from the next cyclical trend of SPAs being the "correct" way to build websites for *insert reasons here* 🤷‍♂️

This is a little reason why I dislike Next's API choices. Because they always encapsulate back on "next". This is how I want to declare this function instead: function getIp(request) { let forwadedRef = request.headers.get('x-forwarded-ref') } A subtle difference, right?

An interesting and well-written post with some compliments and concerns about React Server Components (and some other gripes about React in general): mayank.co/blog/react-ser…

Haskell proves you don't need null at a high-level. Rust proves you don't need null at a low-level. Why are you still using null, again??

Is your Typescript project using strings everywhere? Probably. @mattphillips.io 🦋 explains why this isn’t such a great idea and how you can make your app even more type safe. Typescript: from stringly typed to strongly typed. mattphillips.io/blog/from-stri…