What’s Driving the 2023 Web Development Revolution? Meta‑Frameworks, Edge & AI

Although I personally felt that the outlook for web development slowed between 2016 and 2021, it regained strong attraction last year, as shown by the State of JS 2022 survey.

In this article I introduce the new web‑development trends that will keep developers excited and engaged this year.

Meta‑Frameworks

Single‑page applications (SPA) and their frameworks such as React, Vue, and Svelte have gone through hype cycles and have existed for many years.

With the rise of meta‑frameworks built on top of these solutions, we see a clear shift from client‑side rendering (CSR) to server‑side rendering (SSR).

Today SSR is ubiquitous when using JavaScript frameworks.

The most popular meta‑framework, Next.js, sits on top of React. Its core developer Andrew Clark calls it the “real React 18” because it bundles built‑in features such as Suspense and streaming SSR. Vercel and the React core team collaborate closely to provide an excellent developer experience.

While many developers worry about the close relationship between Next.js and React, alternatives like Remix (now owned by Shopify) take a different approach, treating web standards as first‑class citizens. Competition has led to feature convergence, such as nested routing.

Other frameworks worth watching include:

SvelteKit – built on Svelte, with its latest 1.0 version backed by Vercel.

SolidStart – built on Solid, offering a developer experience that improves on React’s.

Application Rendering Modes

For the past decade, SPAs and client‑side rendering dominated. Developers are now increasingly interested in server‑side rendering (SSR) provided by meta‑frameworks.

The earlier era of multi‑page applications (MPA) already used SSR with JavaScript libraries such as jQuery, MooTools, and Dojo (2005‑2010).

Previously Java (JSP) or Ruby on Rails handled SSR, but now JavaScript drives it.

Next.js has been a major driver of this trend, and other meta‑frameworks like SvelteKit are catching up.

SSR has long competed with static site generation (SSG). While SSG is ideal for static content (e.g., blogs), SSR suits dynamic, user‑centric, authenticated applications.

Beyond SSR and SSG, newer techniques like Incremental Static Regeneration (ISR) and streaming SSR are gaining traction. ISR allows per‑page static rebuilds (e.g., every 60 seconds), while on‑demand ISR can trigger rebuilds via API calls.

Streaming SSR breaks the single‑thread bottleneck by sending rendered chunks to the client progressively.

More granular approaches such as partial hydration, islands (e.g., Astro), and zero‑runtime CSS‑in‑JS solutions (e.g., vanilla‑extract, linaria) are also emerging.

Edge Computing and Serverless

SSR and SSG are closely tied to the edge‑computing and serverless trends, both driven by performance goals.

Serverless functions (AWS Lambda, Google/Firebase Cloud Functions, etc.) let developers deploy individual functions without managing servers, enabling automatic scaling.

Deploying functions close to users reduces latency, creating the concepts of edge computing and edge functions.

Providers such as Cloudflare Workers, Vercel Edge Network, Deno Deploy, and others compete to minimize Time‑to‑Interactive (TTI) for end users.

Beyond performance, edge computing can lower costs by processing data locally instead of sending everything to a central data center.

Database Revival

Serverless has sparked a resurgence of databases. Because each serverless function may open its own connection, connection‑pooling becomes critical.

Popular serverless databases include PlanetScale (MySQL), Neon (PostgreSQL), and Xata (PostgreSQL), offering distributed storage, schema branching, and powerful analytics.

Platforms like Fly.io bundle databases and applications together, while Railway positions itself as a Heroku successor. Supabase provides an open‑source Firebase alternative with hosted databases, authentication, and edge functions.

JavaScript Runtimes

The story began with Ryan Dahl’s 2009 announcement of Node.js, which brought JavaScript to the server using the V8 engine.

Ten years later Dahl introduced Deno as a safer, faster successor, adding TypeScript support and a standard library.

Many cloud providers now ship their own JavaScript runtimes: Cloudflare Workers, Vercel’s runtime, Deno Deploy, and Bun (which runs on JavaScriptCore and is written in Zig).

Fragmentation across runtimes has prompted stakeholders to join the WinterCG initiative to standardize APIs.

Monorepos

Monorepos house multiple projects—applications, packages, components—in a single version‑controlled repository.

Originally used by large applications, they are now common in small companies and open‑source projects for sharing UI components, design systems, and utilities.

Tools such as Turborepo (now owned by Vercel), Nx, Rush, and Lerna enable efficient builds, caching, and dependency management within monorepos.

Utility‑First CSS

Tailwind CSS exemplifies utility‑first CSS, offering excellent developer experience despite some developers finding its markup verbose.

With the rise of SSR, the trade‑offs of CSS‑in‑JS (e.g., increased bundle size and runtime overhead) become more pronounced.

Developers may shift toward SSR‑friendly solutions such as utility‑first CSS paired with pre‑built UI components (e.g., DaisyUI), CSS Modules, or zero‑runtime compile‑time CSS‑in‑JS tools like vanilla‑extract.

End‑to‑End Type Safety

The migration from JavaScript to TypeScript is unstoppable, and full‑stack type safety is becoming a key trend.

Type safety across the API layer can be achieved with OpenAPI for REST or GraphQL Code Generator for GraphQL, generating typed schemas for front‑end code.

tRPC has emerged as a type‑safe alternative to REST/GraphQL, allowing developers to share TypeScript types directly between back‑end and front‑end without intermediate code generation.

Other tools such as Zod, Prisma, and TanStack Router further promote type‑safe full‑stack development.

Build Tools

For years, Create‑React‑App (CRA) dominated the React ecosystem, but Webpack has recently become outdated.

Vite, created by Vue’s Evan You, is the new generation tool for SPAs, offering fast builds thanks to esbuild (written in Go) and a rich ecosystem with Vitest and other plugins.

Vercel’s Turbopack, led by Webpack creator Tobias Koppers, aims to be the successor to Webpack and is expected to pair well with Next.js.

AI‑Driven Development

Will AI replace developers? No definitive answer, but AI‑assisted development is already real.

GitHub Copilot lets developers pair program with an AI inside their IDE, auto‑completing code based on comments.

OpenAI’s ChatGPT can perform coding tasks, serve as a StackOverflow alternative, and generate content, though it also contributes to SEO‑spam concerns.

Summary

Additional noteworthy items that didn’t fit into the main trends:

Tauri as an Electron alternative for building desktop apps with JavaScript, CSS, and HTML.

Playwright as a replacement for Cypress in end‑to‑end testing.

Warp and Fig as next‑generation terminals.

CSS container queries as a replacement for media queries in responsive design.

htmx for creating interactive UIs without JavaScript.

These items round out the landscape of emerging tools and practices for modern web development.