Newsletter
Join the Community
Subscribe to our newsletter for the latest news and updates
Nuxt starter template from the Vercel examples collection that uses Vercel KV for Redis to count and display pageviews.

Full-stack React starter built on TanStack Start with file-based routing, route loaders, TanStack Query, TanStack Store, Tailwind CSS, and Vitest.

A Turborepo monorepo starter pairing a Hono API app with a Next.js web app and shared TypeScript, ESLint, and Prettier configs.

Next.js example app implementing the OpenID Connect Authorization Code Flow with PKCE via Auth.js, deployable to Vercel or Cloudflare Pages.

A production-ready React Router template for full-stack React apps with SSR, HMR, TypeScript, Tailwind CSS, and Docker deploy configs.
Redis Nuxt.js Starter is a Nuxt template from the Vercel examples repository that stores a pageview counter in Vercel KV for Redis and renders the running total back to visitors.
Redis Nuxt.js Starter is a Starter-category Nuxt template published inside the public vercel/examples repository, built to demonstrate a Redis-backed pageview counter. Each page request increments a counter stored in Vercel KV for Redis and the updated number is returned to the browser, with the interface styled using Tailwind CSS. It runs on the Nuxt framework and is meant to be deployed to Vercel, where the Redis integration is attached to the project during deployment. A hosted demo of the counter is available at kv-redis-nuxt.vercel.app.
It provides a Nuxt application that counts pageviews using Vercel KV for Redis. Every visit increments a stored counter, and the current total is displayed on the page, giving a minimal working example of a Nuxt app reading and writing a hosted Redis store on Vercel.
The template code is part of the public vercel/examples repository and can be cloned or deployed at no cost for the code itself. Any charges relate to the Vercel project and Redis integration you connect when deploying, so review your own account limits.
It uses Redis, accessed through Vercel KV. The deploy URL includes a Redis integration product entry, so the datastore is provisioned as part of the deployment rather than being configured manually in the code.
Yes. The README documents scaffolding the example with nuxi init pointed at the storage/kv-redis-nuxt path, then running the development server locally before deploying to Vercel through the standard project flow.
Yes. The Blob starter and the Postgres starter are listed as related templates, covering object storage and relational Postgres persistence respectively instead of Redis.