toolchains-init

Set up the toolchains you usually add after creating a new app or package.

toolchains-init runs the official initializers for the tools you choose, then applies the small workspace setup those tools expect: editor settings, package scripts, router files, test config, API mocking, and release tooling.

Quick Start

Run it from your app directory:

npx toolchains-init
yarn dlx toolchains-init
pnpm dlx toolchains-init

Then choose what you want to add from the interactive prompt.

Key Features

• Official setup commands: runs each tool's own initializer instead of copying a template.
• Pick only what you need: routing, API mocking, E2E, formatting, linting, dead-code checks, release tooling, or editor SDKs.
• Cataloged prompt: toolchains are grouped by app foundation, quality, release, and editor setup.
• Automation friendly: select toolchains and pass their generated CLI arguments in one non-interactive command.
• Fresh project friendly: designed for newly scaffolded apps and packages.
• Monorepo support: initialize an app package from the workspace root with --target.
• Package-manager aware: works with npm, yarn, pnpm, Bun, and Deno.
• Overwrite warnings: shows files that may be replaced before continuing.

What It Can Add

| Toolchain | What You Get | Setup Source | | --------------- | --------------------------------------------------- | -------------- | | TanStack Router | File-Based Routing or Code-Based Routing setup | Official CLI | | Hot Updater | React Native OTA update initializer | Official CLI | | Playwright | Browser E2E test setup | Official CLI | | Storybook | React Vite component workshop setup | Official CLI | | MSW | Browser API mocking worker setup | Official CLI | | oxfmt | Oxc formatter setup and editor integration | Official CLI | | Prettier | Prettier formatter setup and editor integration | Built-in setup | | oxlint | Oxc linter setup and editor integration | Official CLI | | ESLint | ESLint config initializer and editor integration | Official CLI | | Biome | Biome formatter/linter setup and editor integration | Official CLI | | Knip | knip package script | Built-in setup | | React Doctor | react-doctor package script | Built-in setup | | Changesets | Changeset release workflow | Official CLI | | Yarn SDKs | Yarn PnP editor SDKs for VS Code | Official CLI |

Usage

Run the interactive flow:

toolchains-init

Each managed CLI-backed toolchain has a manifest-generated argument group. Select it with --<tool> and forward an upstream option with --<tool>.<flag>[=value]:

toolchains-init \
  --playwright \
  --playwright.browser=chromium \
  --playwright.lang=TypeScript \
  --tanstack-router \
  --tanstack-router.tailwind \
  --yes

Group names come from the generated CLI manifests, so TanStack Router uses --tanstack-router. Boolean flags need no value; string and enum flags accept =<value>. The group selects the toolchain and the namespaced options are forwarded without shell parsing.

Run focused help to see every currently generated option, type, and enum value for one tool:

toolchains-init --playwright --help
toolchains-init --tanstack-router --help

Generated manifests own this public argument surface. When upstream adds a supported flag, the next manifest refresh makes it appear in help and parsing without a handwritten parser or adapter mapping. Adapter-owned locked or blocked values can still reject an incompatible override before setup begins.

Rare wrapper-owned choices use the separate --<tool>.setup.<name> namespace shown in focused help. This namespace cannot collide with generated upstream flags; for example, Router mode is --tanstack-router.setup.router-mode=file.

Non-interactive runs require explicit --<tool> selectors. This keeps an automated command stable when another adapter is added to the registry; --yes never expands silently to every tool.

Choose the package manager explicitly when environment-based detection is not enough:

toolchains-init --package-manager pnpm --tanstack-router --tanstack-router.setup.router-mode=file --msw --yes

Supported values are npm, pnpm, yarn, bun, and deno.

Hot Updater and ESLint are marked interactive-only because their official initializers still require project-specific prompts after the documented CLI arguments are supplied. Their generated groups remain usable, but run them without --yes instead of relying on brittle prompt automation:

toolchains-init --hot-updater
toolchains-init --eslint

Choose a router mode:

toolchains-init --tanstack-router --tanstack-router.setup.router-mode=file --yes
toolchains-init --tanstack-router --tanstack-router.setup.router-mode=code

Code-Based Routing still uses TanStack Router's interactive CLI, so it cannot be combined with --yes.

Run without installing dependencies or official initializers:

toolchains-init --no-install

Monorepos

From a workspace root, point toolchains-init at the app package:

npx toolchains-init --target apps/web
yarn dlx toolchains-init --target apps/web
pnpm dlx toolchains-init --target apps/web

All files, installs, and setup commands run inside the target directory.

For a non-interactive monorepo setup, combine the target with generated tool groups:

npx toolchains-init \
  --target apps/web \
  --package-manager pnpm \
  --tanstack-router \
  --msw \
  --playwright \
  --playwright.browser=chromium \
  --tanstack-router.setup.router-mode=file \
  --yes

Notes

Run this in a freshly scaffolded app. Some selected toolchains can overwrite files such as router files, Playwright config, formatter config, linter config, or editor settings.

For fully non-interactive use, select explicit generated groups that exclude help-listed interactive-only initializers and add --yes. Invalid, unavailable, blocked, or unsupported arguments fail before setup begins.