One template, different editions

The basic edition does not need analytics; the team edition does. Everything else is the same. With a separate template for each, every shared bug needs fixing twice.

Keep the complete source, including analytics, and add a config that removes it for the basic edition. Below, basic.json removes the analytics file and its references in the entry point. team.json keeps them.

Example note

The files below show the source, config, and expected output; no commands run here. To try it locally, replace the example repository URL and save the JSON at the path in the command.

Edition

starter/src/main.ts

1import { track } from './analytics'
2 
3track('app-started')
4console.log('Hello')

Create command

Bash

pnpm create preset init my-basic-app --from ./presets/basic.json

Template differences

Both configs take files from starter. The basic edition adds two steps:

exclude leaves out src/analytics.ts.
replace removes the import and call from src/main.ts, so the entry point no longer refers to the deleted file.

The team edition keeps both files. In each edition, the generated package.json name matches the target directory: my-basic-app or my-team-app.

Shared fixes go into the source repository once. New projects use the selected preset when created; projects already generated need updating separately.

Text replacement rules

replace matches exact text. After editing the entry point, check the config's from value too. Creation fails if that text can no longer be found.

This works for small, explicit file differences. Any references that need removing must be listed in the config. The CLI does not analyze module references or convert TypeScript automatically.

See Preset Configs for more operations.