Introduction

Data fetching is one of the most common challenges developers face when building modern web applications. While it might seem straightforward at first, managing server state quickly becomes complex when you need to handle caching, background updates, pagination, and error states. This is where TanStack Query (formerly React Query) comes in—a powerful library that transforms how we think about server state management.

Introduction

In the previous post, we explored what Nitro plugins are and why they’re one of Nitro’s most powerful features. In this tutorial-focused follow-up, we’ll build real Nitro plugins step by step — the kind you’d actually use in production.

By the end, you’ll know how to create plugins for:

• Request logging
• API key authentication
• Response caching
• Feature flags and runtime configuration

All examples use TypeScript and work in Nuxt + Nitro or standalone Nitro apps.

Introduction

Routing has always been one of those “it works… until it doesn’t” parts of web development. As applications grow, routes become harder to reason about, parameters drift out of sync, and refactors turn into a game of whack-a-mole.

TanStack Router was created to solve exactly that problem.

Built with type safety first, TanStack Router flips the traditional routing model on its head. Instead of hoping your routes, params, loaders, and links line up, the router guarantees they do—at compile time.

In this post, we’ll explore what makes TanStack Router different, why it matters, and how to use it effectively in real-world applications.

Introduction

Nitro is a lightweight, runtime-agnostic server framework that lets you build fast APIs and backends deployable anywhere. But what happens when you need more than basic routes? That’s where Nitro plugins come in — a powerful way to hook into Nitro’s runtime and extend its behavior.:contentReferenceoaicite:1

In this post we’ll cover:

• What Nitro plugins are
• How to create one
• Useful plugin ideas you can build for real applications

Introduction

Most backend tutorials stop at “Hello World”. In this two-part series, we’ll go further by using Nitro to build an actual backend application — a food truck / coffee shop API that could realistically power a real product.

In Part 1, we’ll focus on:

• Project setup
• Application structure
• Core API routes (menu, orders, hours)
• Runtime configuration
• Local development

In Part 2, we’ll expand this into:

• Order creation and validation
• Persistence (in-memory → storage)
• Middleware and plugins
• Deployment-ready architecture

This series assumes basic JavaScript/TypeScript knowledge but no prior Nitro experience.

Introduction

In Part 1, we built the foundation of BrewStop, a food truck / coffee shop backend powered by Nitro. We created menu endpoints, business hours, and a basic order flow.

In Part 2, we’ll turn that prototype into something production-ready by adding:

• Input validation
• Persistent storage (using UnJS tools)
• Order status updates
• Middleware & plugins
• Better structure for deployment

This is where Nitro really shines — small additions, big capability.