Issue #43: Hunting High and Low

🎵 There’s no end to the lengths I’ll go to, hunting high and low… 🎵

Today we’re going to dive into some deep technical parts of different metaframeworks and what unites them, and see how these depths’ complexity is artfully hidden from us, consumers, by metaframework authors, making our developer life quality a little bit higher. As always, there’s something preventing that here and there, but I’m sure we’ll figure it out, as usual, with the help of relentless curiosity, continuous innovation, and hard work. Let’s see how exactly.

The Good

Chris Coyier published his 2026 edition of “What To Know in JavaScript” research spanning from the language basics like some new iterator methods up to ecosystem and specifically the metaframeworks part of it. It’s interesting in that if you’d send it to someone away from the JavaScript world asking “So what’s happening there in JS these days?” they’d not be surprised by the consistently chaotic and versatile nature of the answer, starting from foundations and runtimes and through the deepest npm quirks dungeons. In this regard, the concluding “What should I learn” part should have listed some clinical psychology courses probably but do find out what’s there instead, it’s also a good alternative.

React Server Components, mentioned in the research above of course, became one of the most innovative and popular (justified or otherwise) abstractions of the recent years. Now not only pioneering Next.js and somewhat esoteric Waku support that (with the latter having extracted some awesome low-level APIs for accessing the internals recently), but almost all the mainstream React-supporting full-stack tools catching the baton. TanStack Start published their strong and thorough opinion on that matter.

Naturally, to cut down on server sync logic, we’ll use TanStack Query to manage it!

Currently, the metaframework supports RSCs as an experimental feature through a dedicated Vite plugin but the attention to that justifies the robustness of the approach, which was also highly praised by SvelteKit’s creator Rich Harris on one of the recent episodes of PodRocket podcast.

Interestingly, even the tooling ecosystems which do not approve this kind of complexity boosters in modern metaframeworks, like Vike, in fact however directly support these building blocks — as technically, Vite foundations make such kind of integrations almost trivial. Vike’s creator Rom Brillout had said a couple of wise words about that when he was sharing the scene with Tanner Linsley recently.

The Bad

And as many things in this world that enable and empower good people Vite constantly falls victim to bad people. The surge of moderate-to-high severity vulnerabilities in the package was disclosed again just recently (affecting only dev servers using --host but still). Of course, these kinds of vulnerabilities are nothing in comparison with notorious threats like React2Shell (yeah, this one even has a dedicated website!) which in fact still endangers and frightens the whole industry by active exploits. However, dependabots of this world went nuts the last couple of weeks, making my CISO wave the red-stained SBOM printouts like a helicopter propeller in front of my face.

By the way, the complexity of the software supply chain is still one of the reasons for companies to migrate away from Next.js ecosystem to something lighter — like the TanStack toolchain, for example, which enchanted the Railway team to do exactly that and write the nice story about the experience.

We wanted a stack that matches how we actually build: explicit, client-first, and fast to iterate on. […] Builds that took 10+ minutes now finish in under two. The dev server starts instantly. Route changes are type-checked at the boundary. Layouts compose without workarounds.

Of course, changing the stack is not a silver bullet and a single possible improvement option (one of my favourite Next.js-based tools, Codepen.io, from Chris Coyier again, had a decent hurdles story they shared too, but didn’t give up) and sometimes optimizing an already-used tool gives comparable results, but starting from scratch is always refreshing (in all the senses), one cannot deny that.

The Noteworthy

SvelteKit started their April from a traditional retro which mentioned the new best practices guide for Svelte which is an awesome sign of the framework maturity. Among the interesting recent releases the SvelteKit team did I’d like to separately highlight version 2.56.0 which brought some breaking changes but also a lot of technical DX improvements, from TypeScript to cache invalidation parts, and more.

Docusaurus guys publish updates much more rarely but the list of them is always huge, like for the recent version 3.10.0 where the tooling fans can find cool security improvements, DX goodies (bold maximum TypeScript strictness out of the box, who dis?!), and a huge list of bug fixes which is always too underestimated for stable projects like that. The guys even got rid of Lodash in favor of their own utils implementation, how’s that for a challenge?

React Router team had recently published a new interesting release 7.14.0 which (among other things) includes improvements for the aforementioned RSC story on the tool’s side (not surprisingly, experimental too). Their (“React-less” now) Remix metaframework project with its weird destiny continues marching separately with pretty active development. Interestingly, the guys had updated the official website (no more rock gang themes, a bummer!) with respect to the new development strategy, and I accidentally discovered that some cunning cybersquatters from Vercel had stolen remix.dev domain (check it out!) — that was neat, taking into account .dev TLD is the first thing coming to mind when thinking about a software development tool.

Talking about official websites, I had recently updated the Metaframework Records project with the AI usage disclosure (TL;DR — not much at all) and a new Blog page which even hosts the inaugural long-read article on — guess what? — the nature of metaframeworks. I’m going to expand this part of the project further on with a bunch of related ideas too, so stay tuned!

All in all, as you can see, even in the context of constant lavish AI discoveries of these days in the industry, there’s still a lot of room for innovation and developments in the versatile world of full-stack web development, and everyone can find a niche (and a bit) for themselves, whether it’s higher or lower down the magic metaphorical metaframeworks abstractionship tree.

👋