> Asks if 'if err != nil' is really that bad > Screenshot example shows accidental fallthrough from error case to success case Do we really need to discuss further?

At @framer, we've made React hydration 50%+ faster for lots of sites when using Suspense to fetch data. The surprising part: We did that by... adding more Suspense tags. Why does it make hydration faster? Let's explore🔎:

Yessssss! Node just shipped the ability to run TypeScript files directly!

It's never been easier to make beautifully styled text for your CLI. Node's built-in 'styleText' is NICE

Okay, listen. If you're going to fetch in useEffect(...), you should at least make sure that you're handling: - Loading states - Error handling (rejections & HTTP error codes) - Race conditions & cancellation This isn't over-engineering. It's the minimum code to prevent bugs.

pnpm 9.5 is out with the catalogs feature! https://t.co/bSYCQXdBKI Thanks to @gluxon for implementing it

All PM templates from my Google Drive are now free for everyone 🎁 The extended edition: (1/4)

My books are free to read online: – Exploring JavaScript (ES2024 edition) – Deep JavaScript – Tackling TypeScript – Shell scripting with Node.js Retweets appreciated! https://t.co/cYI2ZY048N

If you care about security for your NextJS app, stop using top level "use server" - it's way too easy to leak data Top level "use server" creates endpoints for all exported functions, even if they are never used on the client One accidental export can cause a ton of damage

We're excited to share our plans for the future of ESLint: https://t.co/4joAwfRqkR

Problem: Choosing a React state library is hard. Solution: Consider the tradeoffs. Here are 6 key tradeoffs, with examples: 1. General vs Specific General: Redux, Zustand, Jotai. Specific: React Query, Apollo. These are specifically designed for handling data fetched via

Hey you - with the big React Router app - you should check out the new "Fog of War" feature released in v6.24.0 yesterday which allows effectively infinite scale for your app. It's also very useful in micro-frontend and module-federation architectures. https://t.co/A2a9xCgc7m

Introducing Million Lint 1.0: A VSCode extension that automatically fixes slow React code for you! It's like ESLint, but for performance!

Great news for those extending base TypeScript configs Soon we should be able to use relative paths to the "final" config file ${configDir} placeholder Previously it was confusing, and you had to duplicate many fields in the child configs to use relative paths

Introducing Elysia 1.0「Lament of the Fallen」 Featuring: - Sucrose - Rewritten static analysis - Improved startup time up to 14x - Remove ~40 routes/instance limitation - Faster type inference up to ~3.8x - Eden Treaty 2 - Strict response error check ↓ Link below ↓

The cost of distraction is the person you could’ve become. If you suffer from distraction, read this. My Deep Work routine:

Introducing Million Lint: A VSCode extension that identifies slow code and suggests fixes. It's like ESLint, but for performance!

Apparently some React devs don't know that <input type="date"> exists and think you need a library for that? So I made a really quick demo...

Hello world! Rolldown is now open source on GitHub:

Big update for TypeScript users! 🚫 Stop using compilerOptions#paths ✅ Start using package.json#imports package.json#imports uses Node.js conventions, solving a specific pain point for monorepo folks. Video coming. Too excited, had to insta-tweet. Stay tuned.