Skip to content

Next.js

Terminal window
tinkerise web next my-next-app --typescript --tailwind --eslint
Terminal window
tinkerise web next my-next-app --no-install --package-manager pnpm

Use next when you want:

  • React Server Components and file-based routing
  • Built-in API routes and full-stack patterns
  • A single framework for app UI and backend endpoints
  • Node.js >=20.9.0
  • npx available in your Node install
tinkerise flagNative create-next-app flagNotes
--typescript--typescript or --tsMapping varies by create-next-app version
--tailwind--tailwindAdds Tailwind setup in scaffold
--eslint--eslintEnables linting setup in scaffold
--biome--biomeUse Biome linter/formatter (v16+)
--no-git--skip-git or --disable-gitMapping varies by create-next-app version
--no-install--skip-installSkips dependency install
--package-manager <pm>--use-<pm>Supports npm, pnpm, yarn, bun
--src-dir--src-dirUse src/ directory
--import-alias <alias>--import-aliasImport alias (e.g. @/*, ~/)
--empty--emptyInitialize with no starter content (v15+)
--app-router--appUse App Router
--react-compiler--react-compilerEnable React Compiler (v16+)
--turbopack--turbopack or (none)Uses --turbopack on create-next-app v16.0-v16.1; v16.2+ already defaults to Turbopack
--api--apiHeadless API project (v16+)
  • tinkerise delegates to create-next-app.
  • --yes is auto-injected so all scaffolding runs non-interactively. Options not explicitly passed use create-next-app defaults, including AGENTS.md in current v16.2+ releases.
  • Registry version mappings handle create-next-app flag changes automatically (v14, v15+, v16.0-v16.1, v16.2+).
  • Pass-through args are enabled, so native flags still work.

You get the official Next.js scaffold output, including:

  • app/ or src/app/ route structure (depending on options)
  • Next.js config, TypeScript config, and package scripts
  • Optional Tailwind and ESLint setup based on selected flags

See full CLI flags: /reference/commands/