Skip to main content

Newsletter Roundup — Week of March 24 📬

· 4 min read
Gergely Sipos
Gergely Sipos
Frontend Architect

Here's what caught our eye this week across JavaScript Weekly, React Status, and Node Weekly — and what it means for the Aliz stack. This is our first newsletter roundup post: a new recurring format where we distill the highlights so the team doesn't have to read three inboxes.

JavaScript Ecosystem​

Solid v2.0.0 Beta — Async Goes Native​

Featured in JavaScript Weekly: the first beta for SolidJS 2.0 has shipped, and the headline feature is first-class async support. The reactive graph can now natively suspend and resume around Promises and async iterables — no more reaching for createResource as a bolt-on utility. Async is a core primitive of the framework.

Why does this matter beyond the Solid community? Because frameworks are converging on the same insight: async shouldn't be an afterthought. React has Suspense and Server Components. Solid now bakes it directly into the reactive core. The direction of travel is clear.

Aliz stack connection: We use React as our UI library, not Solid. But Solid's innovations routinely influence the broader ecosystem — ideas that start in Solid tend to show up everywhere within a year or two.

Ecosystem Highlights​

  • TypeScript in the 5.x era — The type system keeps getting more expressive with each minor release. TypeScript is our baseline for all new projects, so every improvement lands directly in our developer experience.
  • TC39 proposals advancing — Several Stage 3 proposals are moving toward inclusion. Worth keeping an eye on the TC39 proposals tracker for what's coming to the language next.

React Ecosystem​

React 19 and Compiler Updates​

The React ecosystem continues to mature around React 19.x. A few developments worth tracking:

  • React Compiler adoption is growing. The compiler reduces the need for manual useMemo and useCallback by optimizing re-renders automatically. We flagged this in our React docs — it's increasingly relevant as projects adopt React 19.
  • Server Components and async patterns keep evolving. There's a thematic link to the Solid story above: both ecosystems are treating async as a first-class concern rather than something you bolt on at the component level.
  • TanStack ecosystem evolution — TanStack Query, our recommended data-fetching layer, continues to tighten its integration with frameworks. The library's server-side prefetching story is getting better with each release.

Node.js Ecosystem​

Runtime and Tooling Updates​

  • Node.js 22.x LTS updates continue. A good reminder: Vite 8 requires Node.js 20.19+ or 22.12+, so make sure your local environment and CI pipelines are up to date.
  • Runtime competition is driving improvements. Deno and Bun keep pushing Node.js to ship faster — better performance, native TypeScript support experiments, and improved permission models. For Aliz, Node.js remains the default runtime. Our Node.js learning resources cover the fundamentals.
  • Rust toolchain convergence — Rolldown (in Vite), SWC, and Oxc are all maturing rapidly. This is exactly why Vite 8's Rolldown-powered bundler is as fast as it is. The JavaScript ecosystem's build layer is steadily rewriting itself in Rust, and we're already benefiting.

What This Means for the Aliz Stack​

A few threads connect these stories back to our choices:

  • Async-first is the trend. Every framework is investing in better async primitives. This validates our bet on TanStack Query as the server-state layer — it was async-first from day one.
  • Rust toolchains are already paying off. We don't have to wait for this trend to mature. Vite 8 ships Rolldown today, and the speed difference is tangible.
  • Ecosystem alignment matters. Our Recommended Tech Stack is reviewed periodically for exactly these kinds of shifts. When the ecosystem moves, we evaluate whether our defaults should move with it.

If you spot something in the weeklies that should be on our radar, drop a message in the Web Hub channel.

tip

This is our first newsletter roundup post. If this format is useful, we'll make it a recurring thing. Let us know!

Further Reading​