I like React. I really do. It is the default answer for modern web development, and it is that answer for a reason. Generally when React adds a feature it is well thought through, within the React system of thinking.
I may be late to the party, but LangGraph lets you build complex workflow architectures and codify them as powerful automations. Also LLMs, if you want. But you don’t have to! I always liked the idea of “flow-based” programming. PureData, DaVinci Resolve, Node Red... they all appeal to me.
You’re going to hate me for saying this, but I actually like being on-call. I know. I know. But hear me out. Obviously not the part where PagerDuty yanks you out of a dream with your heart pounding. But on-call taught me more about frontend quality than any bug tracker ever did.
Today we are happy to announce the release of Jest 30. This release features a substantial number of changes, fixes, and improvements. While it is one of the largest major releases of Jest ever, we admit that three years for a major release is too long.
I'm using agents to write a lot of code now. Just 6 months ago it didn't really work well, so if you haven't tried in a while, this is your sign. Let me explain practically how I've been using them, where they still kind of suck, and what tools I've had success with.
Tech execs are mandating LLM adoption. That’s bad strategy. But I get where they’re coming from. Some of the smartest people I know share a bone-deep belief that AI is a fad — the next iteration of NFT mania.
I've been facilitating the EventStorming sessions for years now, and something keeps catching my attention. While teams naturally focus on mapping out those orange event sticky notes (the backbone of any EventStorming session), they often underestimate the power of two critical elements: Hot Spots and Notes.
React Server Components (RSC) is a programming paradigm that lets you express a client/server application as a single program spanning over two environments. Concretely, RSC extends the module system (the import and export keywords) with novel semantics that let the developer control the frontend/backend split.
Search params have been historically treated like second-class state. They're global, serializable, and shareable — but in most apps, they’re still hacked together with string parsing, loose conventions, and brittle utils. This works, but it’s manual and repetitive.
At CodeRabbit, we recently shipped our free VS Code extension, bringing context-rich AI-powered code reviews directly into your editor. Our engineering philosophy has always been simple: we build tools that fit seamlessly into your existing workflow. While developers have told us our comprehensive PR reviews have helped them ship faster and keep more bugs from production, many also asked for IDE reviews to help check code prior to sending a pull request.
“It’s Just JavaScript!” is probably a phrase you’ve heard before. I’ve used it myself a number of times.It gets thrown around a lot, often to imply that a particular project is approachable because it can be achieved writing the same, ubiquitous, standardized scripting language we all know and love: JavaScript.
Vitest 3.2 focuses on improvements to Browser Mode and TypeScript support. This release also includes some new useful methods, config options and deprecates the workspace config in favour of projects. In an effort to simplify the configuration, the team decided to deprecate the separate vitest.
Technical documentation is the backbone of any successful engineering team, yet at Pinterest, it has consistently been a source of frustration. Despite using popular web-based wiki tools and experimenting with well-known alternative applications, our internal developer surveys reveal that documentation remains a top pain point.
JavaScript will soon have a new feature that many developers are eagerly awaiting. The feature is the Temporal API which will fix many problems and inconveniences of the old Date object.
So! Suppose you’re an intrepid engineer in a nascent Developer Productivity team. Your engineering organization has decided that it wants to move towards a monorepo.
MCP rapidly enhances AI capabilities but introduces security challenges through its distributed architecture. Especially, the distributed nature of MCP requires a lot of NHIs and their secrets. Our research shows that MCP is a new source of leaks that already discloses real-world secrets.
Developers are moving past AI as just tooling and starting to treat it as a new foundation for how software gets built. Many of the core concepts we’ve taken for granted — version control, templates, documentation, even the idea of a user — are being rethought in light of agent-driven workflows.
At React Conf last summer we announced that Remix was going to "take a nap". Remix v2 had become such a thin wrapper around React Router that an artificial separation developed between the two projects.
Thanks to Server Actions, developers are able to execute server-side code on user interaction, without having to create an API endpoint themselves. I’ve emphasised “themselves”, because server actions are a syntactic sugar for API endpoints, which to my surprise, is not that well-known amongst some professionals in the industry.
Key Takeaways AI design patterns are repeatable solutions for common problems in modern AI-driven software, saving teams from reinventing solutions. We group them into five buckets: Prompting & Context, Responsible AI, User Experience, AI-Ops, and Optimization Patterns.
This is a short story of how humans are still so much more capable of LLMs. Note that I'm not anti-AI or alike, you know it if you know me / follow me somewhere. I use LLMs routinely, like I did today, when I want to test my ideas, for code reviews, to understand if there are better approaches than what I had in mind, to explore stuff at the limit of my expertise, and so forth (I wrote a blog post about coding with LLMs almost two years..
As part of Shopify’s push for faster build pipelines, we began adopting JavaScript modules as a core platform primitive. However, after migrating our Online Store Editor to use modules, developers started reporting issues.
TL;DR: Try out the Rolldown-powered Vite today by using the rolldown-vite package instead of the default vite package. It is a drop-in replacement, as Rolldown will become the default bundler for Vite in the future. Switching should reduce your build time, especially for larger projects.
Choosing a Router is probably one of the most important architectural decisions we have to make. The router isn't just another dependency in node_modules - it's what holds your whole application together.
A.B.A: always be automating Thomas A. Limoncelli Let me tell you about two systems administrators I know. Both were overloaded, busy IT engineers. Both had many repetitive tasks to do. Both wanted to automate these tasks.
Welcome to the next episode in our GitHub for Beginners series, where we’re diving into the world of GitHub Copilot. This is our sixth episode, and we’ve covered quite a lot of ground. You can check out all our previous episodes on our blog or as videos.