@teispace/next-maker 5.0.5 → 5.0.7

package/CHANGELOG.md

@@ -1,5 +1,19 @@
 # Changelog
 
+## [5.0.7](https://github.com/teispace/npm-packages/compare/next-maker-v5.0.6...next-maker-v5.0.7) (2026-09-06)
+
+
+### Bug Fixes
+
+* **next-maker:** shape an app added to an existing workspace like its siblings ([#174](https://github.com/teispace/npm-packages/issues/174)) ([81f2bde](https://github.com/teispace/npm-packages/commit/81f2bdec94b7f45d39eba1966af0b8a89ce04cb0))
+
+## [5.0.6](https://github.com/teispace/npm-packages/compare/next-maker-v5.0.5...next-maker-v5.0.6) (2026-09-06)
+
+
+### Bug Fixes
+
+* **next-maker:** switch variants instead of merging them ([#172](https://github.com/teispace/npm-packages/issues/172)) ([8e393d9](https://github.com/teispace/npm-packages/commit/8e393d91f033a47b9232da046c8b3cda7255749b))
+
 ## [5.0.5](https://github.com/teispace/npm-packages/compare/next-maker-v5.0.4...next-maker-v5.0.5) (2026-09-06)
 
 

package/README.md

@@ -94,7 +94,7 @@ acme/
   .github/workflows/ci.yml                            (--no-ci to skip)
 ```
 
-Git hooks, CI, Docker, community files, and the lockfile are root concerns, so those options are forced off inside the apps. The generated root README explains how to add a shared package (`pnpm add @acme/ui --workspace`), add another app, and build one app's Docker image with `turbo prune`. Only pnpm is supported for workspaces.
+Git hooks, CI, Docker, community files, and the lockfile are root concerns, so those options are forced off inside the apps. The generated root README explains how to add a shared package (`pnpm add @acme/ui --workspace`), add another app, and build one app's Docker image with `turbo prune`. Only pnpm is supported for workspaces. Running `init` inside an existing workspace is enough to add an app later: it detects the root, forces the root-owned options off, drops the app-level package-manager pin, lockfile and npm config, points shared ranges at the root catalog, and installs from the root.
 
 ## setup, remove, doctor, upgrade
 
@@ -110,7 +110,7 @@ npx @teispace/next-maker upgrade --dry-run        # to the starter tag this CLI
 npx @teispace/next-maker upgrade --to v2.1.0
 ```
 
-`setup` and `upgrade` share one engine: the starter is composed twice (old answers and new answers, or old tag and new tag) with the project's identity, formatted with the project's Biome, and the project is three-way merged against the two trees. Lines the project never touched follow the starter, files a feature adds appear, files it owns disappear, anchored lines in shared files (a reducer registration, a provider import) merge in place, and `package.json` merges key by key. Where the project and the starter changed the same lines (a generator registered a slice on the line a feature toggle rewrites), the block is merged again by token, so a registration the project added survives next to one the starter removed or added. Only edits to the same token conflict; those get `<<<<<<<` markers and are listed. Files a command writes are formatted with the project's Biome before it returns. `--dry-run` shows the file-by-file outcome first.
+`setup` and `upgrade` share one engine: the starter is composed twice (old answers and new answers, or old tag and new tag) with the project's identity, formatted with the project's Biome, and the project is three-way merged against the two trees. Switching a variant is not a merge: the files an overlay ships are taken whole, the paths the old variant owned are dropped even when the project wrote to them, and the JSX and call unwraps the change carries are applied to the project directly. Code of your own that still imports a package the change removed is listed by name. Lines the project never touched follow the starter, files a feature adds appear, files it owns disappear, anchored lines in shared files (a reducer registration, a provider import) merge in place, and `package.json` merges key by key. Where the project and the starter changed the same lines (a generator registered a slice on the line a feature toggle rewrites), the block is merged again by token, so a registration the project added survives next to one the starter removed or added. Only edits to the same token conflict; those get `<<<<<<<` markers and are listed. Files a command writes are formatted with the project's Biome before it returns. `--dry-run` shows the file-by-file outcome first.
 
 `doctor` compares the project with the footprint of every feature its record says is on (files, packages, scripts), `--fix` restores what is missing from a pristine starter checkout, and `--compile` runs the project's type-check, which is the only honest signal that the pieces still fit.