@teispace/next-maker 5.0.4 → 5.0.6
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +14 -0
- package/README.md +1 -1
- package/dist/index.js +154 -154
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,19 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## [5.0.6](https://github.com/teispace/npm-packages/compare/next-maker-v5.0.5...next-maker-v5.0.6) (2026-09-06)
|
|
4
|
+
|
|
5
|
+
|
|
6
|
+
### Bug Fixes
|
|
7
|
+
|
|
8
|
+
* **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))
|
|
9
|
+
|
|
10
|
+
## [5.0.5](https://github.com/teispace/npm-packages/compare/next-maker-v5.0.4...next-maker-v5.0.5) (2026-09-06)
|
|
11
|
+
|
|
12
|
+
|
|
13
|
+
### Bug Fixes
|
|
14
|
+
|
|
15
|
+
* **next-maker:** let locale and component run without a terminal ([#170](https://github.com/teispace/npm-packages/issues/170)) ([fa818d9](https://github.com/teispace/npm-packages/commit/fa818d94868e726d389a6cb27ea90fc414a09198))
|
|
16
|
+
|
|
3
17
|
## [5.0.4](https://github.com/teispace/npm-packages/compare/next-maker-v5.0.3...next-maker-v5.0.4) (2026-09-06)
|
|
4
18
|
|
|
5
19
|
|
package/README.md
CHANGED
|
@@ -110,7 +110,7 @@ npx @teispace/next-maker upgrade --dry-run # to the starter tag this CLI
|
|
|
110
110
|
npx @teispace/next-maker upgrade --to v2.1.0
|
|
111
111
|
```
|
|
112
112
|
|
|
113
|
-
`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.
|
|
113
|
+
`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.
|
|
114
114
|
|
|
115
115
|
`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.
|
|
116
116
|
|