Next.jsReactStarter

nextarter-chakra — Next.js Starter Template

By agustinusnathaniel

nextarter-chakra is a starter template based on the Next.js App Router, preconfigured with Chakra UI and TypeScript and integrating tools such as Biome, Playwright, and Turborepo for quickly initializing frontend projects.

Explore the design

Compare the page layouts and mobile experience. Open any screenshot for a closer look.

2 previews
Desktop homepage1 / 2
Desktop captureTop of page

Actual screenshot captured by the server browser.

All pages & views 2

Screenshots show visual appearance; interactive behavior may differ.

Recorded 2026-09-30View source

What stands out

A quick read of the recorded project description.

01

Bootstrapped with the Next.js App Router and create-next-app

02

Built-in Chakra UI and TypeScript configuration for immediate development

03

Split-Layer structure separating routing entry points, business logic, and shared UI components

04

Integrates Biome formatting and checks, Playwright end-to-end testing, and the Turborepo build system

05

Provides deployment buttons for Vercel, Netlify, and Railway plus a StackBlitz online open entry

06

Uses pnpm as the package manager and includes theme switching and React Icons support

Template Details

nextarter-chakra is maintained by agustinusnathaniel and the repository is MIT-licensed. It is a starter template (boilerplate) for initializing Next.js applications. It is bootstrapped with create-next-app and additionally includes Chakra UI and TypeScript configuration, so a project has a component library and type system out of the box.

The template uses a Split-Layer structure that separates Next.js routing from React UI logic: src/app holds the App Router entry points (layout.tsx provides the global RootLayout and Providers, and page.ts re-exports Home from lib/pages); src/lib carries business logic, including layout (shell components such as Header and Footer), pages (page implementations), and styles (theme configuration); src/components holds shared UI components, with the ui subdirectory containing basic primitives such as buttons and inputs.

On the tooling side, the template integrates Biome for formatting and static checks, Playwright for end-to-end testing, and Turborepo as the build system. Icons use React Icons, theme switching relies on next-themes, and the styling engine is Emotion as used by Chakra UI. The package manager is specified as pnpm. The README provides deployment buttons for Vercel, Netlify, and Railway as well as a StackBlitz online open entry, and gives commands for installing dependencies, starting the development server, production builds, running E2E tests, and Biome check/fix.

Usage limitations: the template itself only provides the initial project structure and tool configuration, with no business features. Demo screenshots and third-party assets must be checked against their respective licenses, and external hosting, database, and other services may incur separate charges.

Next.jsReactStarter

Is it right for your project?

Use Cases

  • Quickly setting up a new Next.js project with the Chakra UI component library and a TypeScript type system
  • Teams that want a project to start with a layered structure separating routing and UI logic
  • Projects that need to use Biome for code checks and Playwright for end-to-end testing directly in the template
  • Developers who want to quickly preview and deploy via Vercel, Netlify, Railway, or StackBlitz

Suitable For

  • Frontend developers using Next.js and React
  • Teams that prefer Chakra UI as their component library
  • Projects that need TypeScript and code quality tools preconfigured
  • Individuals or organizations that want to start from MIT-licensed code

Getting started & customization

Use these recorded setup notes alongside the repository instructions for your chosen version.

  1. 1

    The project uses pnpm; first run pnpm install to install dependencies

  2. 2

    Run pnpm dev to start the development server, accessible by default at http://localhost:3000

  3. 3

    Run pnpm build for a production build

  4. 4

    Run pnpm test:e2e to run Playwright end-to-end tests

  5. 5

    Use pnpm biome:check to check for code issues and pnpm biome:fix to automatically fix them

Read repository instructions

License & source material

Usage conditions & limitations

Free to use · keep license notice

This entry covers the free version in the public repository under the MIT license; the free scope is the code of that version and does not mean external services or third-party assets are free.

Must comply with when using

  • The code of this version may be used, modified, used commercially, and distributed for free.
  • When distributing copies or substantial portions of the code, retain the original author's copyright notice and the complete MIT license notice.
  • The code is provided as is; warranties and limitations of liability are governed by the original license and applicable law.

Additional costs & items to verify

  • Demo images, fonts, icons, and other third-party assets must be checked against their respective licenses and cannot be judged solely by the code's MIT license.
  • External services such as domains, hosting, databases, payments, or AI may incur separate charges.
View Original Text Basis

Compiled by DeepSeek based on repository license and README ·2026-09-30. Results only cover the materials read; dependencies, images, fonts, and subsequent term changes are subject to their respective original texts.

Project checks & description sources

Template Information

Source platforms
GitHub
Documentation and maintenance reference score
More documented · 96 / 100
Technologies
Next.js · React
Website type
Starter
How this score is calculated

Our heuristic uses license records (up to 30), a demo link (12), a preview (10), stars (15), recorded maintenance (15), description completeness (8), feature records (5) and classification data (5). It is not a code, security or performance test, or a Google score. A link does not establish tested functionality.

What to verify for this project

Repository update recorded
2026-09-28
Screenshot last checked
2026-09-30

A demo link is listed. Check it with your own content and viewport sizes; its presence does not confirm that forms, authentication or payments work.

The catalog identifies Next.js as the primary stack. Check the actual dependency manifest and lockfile for versions and hosting requirements. These notes use recorded metadata, not a code audit or a deployment test.

Use a selection guide →

How this description was prepared

AI-assisted description based on catalog records and repository material. Repository authors are not automatically the reviewers of this description.

Automatically checked against source and license rules; no manual editorial review.

Inspect the recorded source material

SHA-256: 8122fb81831da804d45e2f78ca0cff6442cfbd43c1188b60d79a10f3991baf16

2026-09-30T08:07:54.102Z

Source file / repository
# nextarter-chakra

<img src="https://og.sznm.dev/api/generate?heading=nextarter-chakra&text=Next.js+template+with+Chakra-UI+and+TypeScript+setup.&template=color&center=true&height=330" />

<div align="center">
  <a href="https://vercel.com/new/clone?repository-url=https%3A%2F%2Fgithub.com%2Fagustinusnathaniel%2Fnextarter-chakra" target="_blank"><img src="https://vercel.com/button" alt="Deploy with Vercel" /></a> <a href="https://app.netlify.com/start/deploy?repository=https://github.com/agustinusnathaniel/nextarter-chakra" target="_blank"><img src="https://www.netlify.com/img/deploy/button.svg" alt="Deploy to Netlify" /></a> <a href="https://railway.app/new/template/aqmmai?referralCode=9lKVVo" target="_blank"><img src="https://railway.app/button.svg" alt="Deploy on Railway" height="32px" /></a>

<a href="https://stackblitz.com/github/agustinusnathaniel/nextarter-chakra" target="_blank"><img src="https://developer.stackblitz.com/img/open_in_stackblitz.svg" alt="Open in StackBlitz" /></a>

  <p>This is a <a href="https://nextjs.org/" target="_blank">Next.js</a> project bootstrapped with <code>create-next-app</code>, added with <a href="https://chakra-ui.com" target="_blank"><b>Chakra UI</b></a> and <a href="https://www.typescriptlang.org" target="_blank"><b>TypeScript</b></a> setup. <br/> Start developing right away!</p>

</div>

This is a **Next.js + Chakra UI + TypeScript** starter template packed with modern tooling setup.

## 🚀 Features

-   **Framework**: [Next.js 16](https://nextjs.org/) (App Router)
-   **UI Library**: [Chakra UI v3](https://chakra-ui.com/)
-   **Styling Engine**: Emotion (via Chakra UI) + [next-themes](https://github.com/pacocoursey/next-themes)
-   **Language**: [TypeScript 5](https://www.typescriptlang.org/)
-   **Linting & Formatting**: [Biome](https://biomejs.dev/)
-   **E2E Testing**: [Playwright](https://playwright.dev/)
-   **Build System**: [Turborepo](https://turbo.build/repo)
-   **Icons**: [React Icons](https://react-icons.github.io/react-icons/)

## 🏗 System Architecture

This project uses a **Split-Layer** architecture to separate Next.js routing concerns from React UI logic.

```mermaid
graph TD
    subgraph "Routing Layer (src/app)"
        L[layout.tsx] --> Providers
        P[page.ts] --> Logic
    end

    subgraph "Logic Layer (src/lib)"
        Providers --> Layout[Layout Component]
        Layout --> Header
        Layout --> Footer
        Logic --> HomePage[Page Component]
    end

    subgraph "UI Layer (src/components)"
        HomePage --> Components
        Header --> Components
        Footer --> Components
    end
```

## 📂 Repository Structure

The code is organized to keep business logic and routing separate:

```bash
src/
├── app/            # Next.js App Router (Entry points)
│   ├── layout.tsx  # Global RootLayout & Providers
│   └── page.ts     # Re-exports Home from lib/pages
├── components/     # Shared UI components
│   └── ui/         # Primitives (Buttons, Inputs, etc.)
└── lib/            # Application Business Logic
    ├── layout/     # Shell components (Header, Footer)
    ├── pages/      # Page implementations (Home, etc.)
    └── styles/     # Theme configuration
```

## 🛠 Getting Started

### 1. Install Dependencies

This project uses [pnpm](https://pnpm.io/).

```bash
pnpm install
```

### 2. Run Development Server

```bash
pnpm dev
```

Open [http://localhost:3000](http://localhost:3000) to view it in the browser.

### 3. Build for Production

```bash
pnpm build
```

### 4. Run Tests

```bash
pnpm test:e2e
```

## 🧹 Code Quality

We use **Biome** for fast formatter and linter.

```bash
# Check code issues
pnpm biome:check

# Fix issues automatically
pnpm biome:fix
```
Report a correction

Explore similar templates

Compare previews and descriptions within the same stack and category.