@teispace/next-maker 5.0.6 → 5.1.0

package/CHANGELOG.md

@@ -1,5 +1,19 @@
 # Changelog
 
+## [5.1.0](https://github.com/teispace/npm-packages/compare/next-maker-v5.0.7...next-maker-v5.1.0) (2026-09-06)
+
+
+### Features
+
+* **next-maker:** compose Markdown, not just code ([#176](https://github.com/teispace/npm-packages/issues/176)) ([b3c35ff](https://github.com/teispace/npm-packages/commit/b3c35ffd0cd18ac928b8116be99468487798acea))
+
+## [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)
 
 

package/README.md

@@ -67,6 +67,12 @@ The starter declares its options in `next-maker.json`; the CLI asks those questi
 
 Presets: `default`, `minimal`, `full`, `zustand`, `spa`. A `--config` file holds identity fields (`name`, `description`, `author`, `version`, `email`, `gitRemote`) plus `packageManager`, `preset`, and `options`.
 
+The manifest's `always` block holds what never reaches a project: `remove`
+for starter-only files, and `anchors` for ids stripped regardless of the
+answers, which is how a documentation paragraph that links those files
+disappears with them. Anchors work in Markdown as well as code, so a table
+row pointing at an optional feature's guide leaves with the feature.
+
 What `init` does, in order: fetch the pinned starter (or `--starter-path` / `NEXT_MAKER_STARTER_PATH`), read its manifest, resolve answers (constraints such as `ws` needing Redux are enforced), apply the package-manager overlay, delete the files of features that are off, copy overlays for chosen variants, strip anchor comments and unwrap provider wrappers, prune `package.json` and `.env.example`, rewrite package-manager commands, stamp the identity, write `README.md` and `.next-maker.json`, install, format, copy `.env`, and initialise git.
 
 Every generated project passes the starter's own gates (`lint`, `type-check`, `check:deprecated`, `test`, `build`); the `smoke` script composes a matrix of option combinations and runs them.
@@ -94,7 +100,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