presetter

Install presetter and the preset packages matching your project shape, such as preset-esm and preset-node for a Node ESM app. Add a presetter.config.ts extending those presets, add package.json delegate scripts, then run bootstrap and verify build, lint, typecheck, and tests.

Encode every deliberate setting from tracked configs into preset variables, scripts, assets, or overrides before deleting anything. Bootstrap, compare generated output against the preserved baseline, add generated paths to the ignore asset, and only then untrack the old files.

Match the stack to the project shape: esm for a plain ESM library, esm plus node for a Node app, next for a Next application, and monorepo plus node plus esm for a workspace root. Do not redundantly add presets that a top-level preset already composes.

Bootstrap overwrites every asset path it generates and never merges with files on disk. Restore the tracked file, encode its intent in the preset or an override, verify the regenerated result matches, and only then untrack the original.

Local package.json scripts intentionally shadow preset tasks at runtime, so a same-named local script wins as the task entry. Run the task with the --template flag to compare against the preset version, and remove the local script if the shadowing was accidental.

Only packages without a closer config inherit the root through nearest-config lookup. A package with its own config stands alone unless it explicitly imports the root config and lists it in extends.