@nanoforge-dev/cli 1.6.2 → 2.3.0

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 ADDED
@@ -0,0 +1,436 @@
1
+ # Changelog
2
+
3
+ All notable changes to this project will be documented in this file.
4
+
5
+ # [2.3.0](https://github.com/NanoForge-dev/CLI/compare/1.6.2...2.3.0) - (2026-09-24)
6
+
7
+ > NanoForge v2 changes **how a game is structured**. In v1 a game was one folder split into
8
+ > `client/` and `server/`, and the CLI rebuilt its entry files from JSON "save" files. In v2 a
9
+ > game is a set of standalone **projects** (client, server, and shared libs). Each project has
10
+ > its own typed `nanoforge.config.ts`, and a **workspace** can group them in one monorepo. Entry
11
+ > files are normal source code that you own. Nothing regenerates them.
12
+ >
13
+ > The CLI repository is now a monorepo, and this release is shared by three packages. Each
14
+ > library has its own changelog with the details:
15
+ >
16
+ > - **[`@nanoforge-dev/config` changelog](https://github.com/NanoForge-dev/CLI/blob/main/libs/config/CHANGELOG.md)**:
17
+ > the new `nanoforge.config.ts` format, its four types, defaults, validation, and the
18
+ > field-by-field migration from `nanoforge.config.json`.
19
+ > - **[`@nanoforge-dev/schematics` changelog](https://github.com/NanoForge-dev/CLI/blob/main/libs/schematics/CHANGELOG.md)**:
20
+ > the generated game in v1 vs v2, the new `workspace` / `project` schematics, the engine v2
21
+ > entry file, the demo game and dependency versions.
22
+ >
23
+ > This section covers what changed in the `nf` CLI itself.
24
+
25
+ ## Why 2.3.0 (and not 2.0.0)
26
+
27
+ The CLI, `@nanoforge-dev/config` and `@nanoforge-dev/schematics` now share **one version
28
+ number** and are released together. That shared version must be higher than the latest
29
+ published version of every package. Schematics was already at **2.2.1** (last release from its
30
+ old repository), so all three packages are **aligned to the schematics version** and released
31
+ as **2.3.0**. The CLI goes from 1.6.2 straight to 2.3.0. There are no CLI 2.0.0, 2.1.x or 2.2.x
32
+ releases.
33
+
34
+ ## Game architecture in short
35
+
36
+ | Concern | v1 | v2 |
37
+ | ---------------- | --------------------------------------------- | ----------------------------------------------------------------------- |
38
+ | Unit of the game | One app with a `client` and a `server` part | Independent `client` / `server` projects (plus libs), grouped by a workspace |
39
+ | Config | One `nanoforge.config.json` | One `nanoforge.config.ts` / `.js` per project, lib and workspace |
40
+ | Entry file | Regenerated from `.nanoforge/*.save.json` | `src/main.ts`, scaffolded once, then yours |
41
+ | Output / assets | `.nanoforge/<part>`, `<part>/static` | `dist/`, `assets/` inside each project |
42
+ | Several apps | Not possible | Every project matched by the workspace's `packages` is built and started |
43
+
44
+ `nf new` creates either a single `client` project (single-player) or a workspace with
45
+ `apps/client` and `apps/server` (multiplayer). The schematics changelog has the full generated
46
+ trees.
47
+
48
+ ## How the CLI reads configs
49
+
50
+ The CLI no longer ships its own JSON config loader (`class-validator` defaults, `-c` file name).
51
+ It uses `@nanoforge-dev/config` to load the config in the command's directory
52
+ (`nanoforge.config.ts`, or `.js` if there's no `.ts`). If neither file exists, the command
53
+ fails with `ConfigNotFoundError`.
54
+
55
+ On top of that, the CLI resolves the workspace (`parseWorkspaceConfig`, `resolveProjects`):
56
+
57
+ - **Root is `client` / `server`:** that project is the only target.
58
+ - **Root is `workspace`:** each `packages` glob is expanded from the root:
59
+ - a matched directory without a config is skipped
60
+ - a glob that matches nothing logs a warning
61
+ - a nested `workspace` throws
62
+ - **Root is `lib`:** error. A lib can't be an entry point.
63
+
64
+ The result is a list of `{ directory, config }` for every client and server project. Libs are
65
+ left out. `build` and `start` loop over this list, and `create` uses it to find its target.
66
+
67
+ ## Code is no longer generated from save files
68
+
69
+ In v1, `main.ts` was build output: the CLI regenerated it from `.nanoforge/<part>.save.json`
70
+ with `nf generate` or `nf dev --generate`. In v2 you write `main.ts` yourself, so the CLI
71
+ drops everything that supported regeneration (#217):
72
+
73
+ - the `generate` command, its action, messages, docs page and e2e suite
74
+ - the `--generate` option of `nf dev`
75
+ - the `initFunctions` input of `nf new`
76
+
77
+ `build --editor` now builds the project's `editor.entryFile`. It defaults to the same
78
+ `src/main.ts`, and nothing editor-specific is added to it any more. In v1, a separate
79
+ generated entry added `Graphics2DEditorLibrary`.
80
+
81
+ ## Command changes
82
+
83
+ ### `nf new` (#218)
84
+
85
+ - The "server?" question now means **multiplayer**, and it decides the architecture:
86
+ - **No:** a single `client` project is generated directly in the target directory.
87
+ - **Yes:** a `workspace` is generated, plus `apps/client` (`hasServer: true`) and
88
+ `apps/server`. Package names become `<name>-client` / `<name>-server`.
89
+ - It calls the new `workspace` and `project` schematics instead of the old chain
90
+ (`application` → `configuration` → `part-base` → `part-main` → `docker`).
91
+ - It forwards `strict`, `packageManager`, `docker` and `editor` to each project.
92
+
93
+ ### `nf build` (#219)
94
+
95
+ - It builds **every client/server project** found in the workspace, instead of looking at
96
+ `client.enable` / `server.enable`.
97
+ - Each target builds, copies assets, resets its output and watches files **inside its own
98
+ project directory**.
99
+ - If there is more than one project, logs show the project path, e.g. `Client (apps/client)`.
100
+ - `--client-entry`, `--client-static-dir`, `--client-out-dir` and their `--server-*`
101
+ equivalents still work. They now override `entryFile`, `dir.assets` and `out.dir` of each
102
+ project of that type.
103
+ - If no assets directory is set, the asset copy step is skipped.
104
+
105
+ ### `nf start` (#220, #224)
106
+
107
+ - It starts **every server project, then every client project**. If it finds no project, it
108
+ fails with a hint to check `packages` or run `nf new`.
109
+ - Each client uses its own `port` and its own `tls` config. `--port`, `--cert` and `--key`
110
+ still override them.
111
+ - `--watch-server-dir` is passed to the client loader only when there is **exactly one**
112
+ server project.
113
+ - `--client-dir` / `--server-dir` now mean **output** directories. They override `out.dir`.
114
+ - Wording changed from SSL to **TLS** in flags, errors and docs. Errors now point to
115
+ `tls.cert` / `tls.key` in `nanoforge.config.ts`.
116
+ - The package manager is detected **once**, from the directory the command runs in (the
117
+ workspace root), not once per loader (#224).
118
+
119
+ ### `nf create` (#222)
120
+
121
+ - It reads the project config to find where to put the file (`dir.components` / `dir.systems`)
122
+ and which language to use.
123
+ - **Client or server is now inferred** from the project's `type`, so `-s, --server` is removed.
124
+ - Running it at a **workspace root** is refused. Run it inside a project, or pass
125
+ `-d apps/client`.
126
+
127
+ ### `nf dev` (#217)
128
+
129
+ - `--generate` is removed. `dev` now just runs `build --watch` (plus `--editor` when asked) and
130
+ `start --watch` side by side.
131
+
132
+ ### `nf generate` (#217)
133
+
134
+ - **Removed.**
135
+
136
+ ## Breaking changes
137
+
138
+ - `nanoforge.config.json` is **no longer read**. Use one `nanoforge.config.ts` / `.js` per
139
+ project. The key mapping is in the
140
+ [config changelog](https://github.com/NanoForge-dev/CLI/blob/main/libs/config/CHANGELOG.md).
141
+ - `nf generate` and `nf dev --generate` are removed.
142
+ - `nf create -s/--server` is removed. The side now comes from the project config.
143
+ - `-c, --config` is removed from `build`, `start` and `create`.
144
+ - `--client-dir` / `--server-dir` on `nf start` now point to **output** directories.
145
+ - `nf new` generates the v2 layout and engine v2 code. See the
146
+ [schematics changelog](https://github.com/NanoForge-dev/CLI/blob/main/libs/schematics/CHANGELOG.md).
147
+ - The CLI now declares `engines.node: "26"`, so **users need Node 26**.
148
+
149
+ ## Migrating a v1 game
150
+
151
+ 1. **Choose the shape.**
152
+ - Client only: keep a single project at the root.
153
+ - Client + server: create a workspace root with `packages: ["apps/*"]`, then move
154
+ `client/` to `apps/client/src/` and `server/` to `apps/server/src/`.
155
+ 2. **Replace `nanoforge.config.json`** with one `nanoforge.config.ts` per project. The
156
+ field-by-field table is in the
157
+ [config changelog](https://github.com/NanoForge-dev/CLI/blob/main/libs/config/CHANGELOG.md).
158
+ 3. **Make `main.ts` yours.** Copy the last generated `client/main.ts` / `server/main.ts` to
159
+ `src/main.ts`. Then remove `.nanoforge/*.save.json` and `.nanoforge/editor/`.
160
+ 4. **Inline init hooks.** Move the contents of `init/before-*.ts` / `after-*.ts` into `main.ts`
161
+ around `app.init()` / `app.run()`.
162
+ 5. **Update engine imports.** For example `@nanoforge-dev/ecs-client` →
163
+ `@nanoforge-dev/ecs/client`, and `Context` from `@nanoforge-dev/common` → `nanoforge`. The
164
+ [schematics changelog](https://github.com/NanoForge-dev/CLI/blob/main/libs/schematics/CHANGELOG.md)
165
+ shows a full v2 entry file.
166
+ 6. **Split dependencies** into a `package.json` per project, and set up your package manager's
167
+ workspace (`pnpm-workspace.yaml` or `"workspaces"`).
168
+ 7. **Move static files** into `assets/`, or set `dir.assets`.
169
+ 8. **Update scripts.** Drop `nf generate` and `--generate`. Instead of `nf create --server`,
170
+ run `nf create` inside the server project.
171
+
172
+ ## Known issues
173
+
174
+ CLI issues:
175
+
176
+ - **Leftover `-c, --config` on `nf dev`.** Its default is still `nanoforge.config.json`, and the
177
+ value is never passed on to `build` / `start`. The configuration docs, `dev.mdx` and the README
178
+ still mention `-c`.
179
+ - **`build` / `start` ignore libs.** `libs` and `lib` configs are discovered but not built or
180
+ linked yet.
181
+
182
+ Issues in the generated code, which users will hit through `nf new` / `nf create` (details in
183
+ the [schematics changelog](https://github.com/NanoForge-dev/CLI/blob/main/libs/schematics/CHANGELOG.md)):
184
+
185
+ - The generated workspace scripts run `nf dev -r`, `nf build -r` and `nf start -r`, but no
186
+ command defines `-r`.
187
+ - `nf create` templates still use v1 imports, so created components and systems don't compile
188
+ in a v2 project.
189
+ - Generated configs import `nanoforge/config`, and the engine v2 packages aren't published yet.
190
+
191
+ ## Repository, tooling & CI
192
+
193
+ - **Monorepo** (#197): a pnpm workspace (`.`, `libs/*`) run by **Turborepo** (`turbo.json`
194
+ with `build`, `build:dev`, `lint`, `format`, `test:unit` and `test:e2e`, remote cache on).
195
+ New root scripts `repo:build`, `repo:lint`, `repo:format`, `repo:test`, `repo:test:unit` and
196
+ `repo:test:e2e`. The Husky pre-push hook runs the `repo:*` versions.
197
+ - **Packages:** `@nanoforge-dev/cli` (root), `@nanoforge-dev/config` (`libs/config`) and
198
+ `@nanoforge-dev/schematics` (`libs/schematics`, previously its own repository). The CLI uses
199
+ both libraries through `workspace:*`. All three share one version and release together.
200
+ - **Releases** (#225): release branches are now named `releases/cli@<version>`. The Release
201
+ workflow publishes config → schematics → cli. The automatic beta release on every merged PR
202
+ is gone. Alpha releases of a single package are still triggered by hand. CONTRIBUTING explains
203
+ the flow.
204
+ - **Commit scopes** `cli`, `config` and `schematics` are documented, and the labels and
205
+ issue/labeler configs were updated for the new packages.
206
+ - **Runtime:** Node **25 → 26** (`.nvmrc`, `engines`), pnpm **11.10 → 12.0**.
207
+ - **Build:** tsdown no longer uses `skipNodeModulesBundle`, because its package-name check also
208
+ matched the `@lib/*` / `@utils/*` path aliases and left them unresolved in the output.
209
+ - **Dependencies:** `@nanoforge-dev/editor` moved from `optionalDependencies` to
210
+ `dependencies`. Loaders went to `^1.5.1` (#227). Vitest 5, tsdown 0.23, Angular DevKit 22.1,
211
+ dotenv 18 and others were bumped (#230). The pnpm catalog `tests` was renamed to `test`.
212
+ - **Docs:** new *Schematics* section. The configuration page was rewritten for the typed
213
+ multi-config model. The `generate` page was removed and the command pages renumbered.
214
+ - **Tests:** the e2e suites for `new`, `build`, `create`, `install` and `new-config` were
215
+ rewritten for the new layout, and `cli-generate` was removed. New unit tests cover the
216
+ workspace config parser and the config loader.
217
+ - **Contributors** list updated (#229).
218
+
219
+ ## Commits
220
+
221
+ ### Bug Fixes
222
+
223
+ - **start:** Change path for detecting package manager (#224) ([ddbed0a](https://github.com/NanoForge-dev/CLI/commit/ddbed0a6bd39383f48b2e4fc71ba015e4df856ae)) by @Exeloo
224
+ - Remove generate command as it's no longer usefull (#217) ([a07acd7](https://github.com/NanoForge-dev/CLI/commit/a07acd7ee01afd9dd17eb15051c15e24dbb19c84)) by @Exeloo
225
+ - **BREAKING CHANGE:** The `generate` command no longer exist
226
+
227
+ ### Documentation
228
+
229
+ - Update links (#212) ([be9f483](https://github.com/NanoForge-dev/CLI/commit/be9f483c76ba841cb9edccfc477fb2b1904c1f5f)) by @Exeloo
230
+
231
+ ### Features
232
+
233
+ - Put network lib in dependencies (#226) ([e2dde26](https://github.com/NanoForge-dev/CLI/commit/e2dde2607736949caf85a057135c23fed8408861)) by @Exeloo
234
+ - Add new project and workspace schematics and remove old ones (#216) ([f551392](https://github.com/NanoForge-dev/CLI/commit/f551392a843d592b1efc70cf4613f98f616999b0)) by @Exeloo
235
+ - Add config parser (#214) ([cde54ab](https://github.com/NanoForge-dev/CLI/commit/cde54abba3a8b8385e6441bff8a39365dffde90c)) by @Exeloo
236
+ - Add schematics (#200) ([330b9be](https://github.com/NanoForge-dev/CLI/commit/330b9bee1084c911aad8291c25aa591f0eb0d340)) by @Exeloo
237
+ - Add config lib and monorepo config files (#197) ([197a75c](https://github.com/NanoForge-dev/CLI/commit/197a75c82699f8a90c14be03208bd6313f53886d)) by @Exeloo
238
+
239
+ ### Refactor
240
+
241
+ - **cli:** Change create command to fit the new architecture (#222) ([3afb463](https://github.com/NanoForge-dev/CLI/commit/3afb463c96d7e511e492a6c8cbe82b686d837a08)) by @Exeloo
242
+ - **cli:** Change start command to fit the new architecture (#220) ([3acb4a1](https://github.com/NanoForge-dev/CLI/commit/3acb4a1e214426a1f5e953774859eba38ca49ffa)) by @Exeloo
243
+ - Change build cmd to new archi (#219) ([6700f71](https://github.com/NanoForge-dev/CLI/commit/6700f71e9d500efea0eb80aaad655623415f489b)) by @Exeloo
244
+ - **cli:** Change new cmd to new archi (#218) ([a2e0d1f](https://github.com/NanoForge-dev/CLI/commit/a2e0d1ffe60063d3f5ae22ed78718e7592fe0f72)) by @Exeloo
245
+
246
+ # [1.6.2](https://github.com/NanoForge-dev/cli/compare/1.6.1...1.6.2) - (2026-07-07)
247
+
248
+ ## Bug Fixes
249
+
250
+ - Set init functions default config to false (#190) ([1981e20](https://github.com/NanoForge-dev/cli/commit/1981e20235b8e67dfe520c3525aca15cbcdfbd23)) by @Exeloo
251
+
252
+ # [1.6.1](https://github.com/NanoForge-dev/cli/compare/1.6.0...1.6.1) - (2026-07-04)
253
+
254
+ ## Bug Fixes
255
+
256
+ - Editor command (#188) ([3cd1d8f](https://github.com/NanoForge-dev/cli/commit/3cd1d8fc62909d5e64fb9ab5969b9cfd4d86aa12)) by @Exeloo
257
+ - **schematics:** Since pnpm v11 we need to resolve the path to schematics ourselves (#185) ([6ba1d3f](https://github.com/NanoForge-dev/cli/commit/6ba1d3f09dac4982b0639cad6d55c860d2da6b55)) by @MartinFillon
258
+
259
+ ## Documentation
260
+
261
+ - Add registry link to login command (#187) ([cbec8dc](https://github.com/NanoForge-dev/cli/commit/cbec8dc21bee49b4ac7874a4f8d22cccb3f4f5b8)) by @Exeloo
262
+ - **ssl:** Add missing config for ssl docs (#184) ([7a4431c](https://github.com/NanoForge-dev/cli/commit/7a4431c3a4f6d5687af5312df0ffd2f78bf5aef3)) by @MartinFillon
263
+
264
+ ## Features
265
+
266
+ - Display npm package link (#182) ([eb0a85c](https://github.com/NanoForge-dev/cli/commit/eb0a85c792152006c205a3de09bb14cfb23f3d91)) by @josephinecr
267
+ - **editor:** Display clickable link when starting editor (#180) ([22c536d](https://github.com/NanoForge-dev/cli/commit/22c536d07e4a6d8a9bad15839989d7bccdc02db3)) by @josephinecr
268
+ - Add ssl config to json configuration (#179) ([10787fd](https://github.com/NanoForge-dev/cli/commit/10787fd37aabfbfe3ecadd234d445e02526e9493)) by @josephinecr
269
+
270
+ # [1.6.0](https://github.com/NanoForge-dev/cli/compare/1.5.3...1.6.0) - (2026-06-23)
271
+
272
+ ## Bug Fixes
273
+
274
+ - Upgrade actions and add repository name to publish docs (#163) ([acc5439](https://github.com/NanoForge-dev/cli/commit/acc5439c8edd2afd016cdcb4aec8be7fd9f4301b)) by @Exeloo
275
+
276
+ ## Documentation
277
+
278
+ - Add full cli docs and guides (#174) ([f618d37](https://github.com/NanoForge-dev/cli/commit/f618d374413a7087a97b422cf301d88efe32a761)) by @Exeloo
279
+
280
+ ## Features
281
+
282
+ - Add read global config on cwd (#173) ([67c0eac](https://github.com/NanoForge-dev/cli/commit/67c0eaca7ac81a44eba45268da01c18120192ff0)) by @Exeloo
283
+ - Add editor flag on dev cmd (#171) ([2af80f5](https://github.com/NanoForge-dev/cli/commit/2af80f503419c6c2155282aea3c58b2a7b934205)) by @josephinecr
284
+ - Add suggestion for error messages (#170) ([c7cb939](https://github.com/NanoForge-dev/cli/commit/c7cb93941d411683da2f00fea74efbdc3f76253a)) by @josephinecr
285
+ - Change error handling to be more specific (#168) ([5329236](https://github.com/NanoForge-dev/cli/commit/532923687b0208a1c26dac16e9d7671591e11666)) by @josephinecr
286
+
287
+ ### New Contributors
288
+
289
+ - @josephinecr made their first contribution in #171
290
+
291
+ # [1.5.3](https://github.com/NanoForge-dev/cli/compare/1.5.2...1.5.3) - (2026-06-04)
292
+
293
+ ## Bug Fixes
294
+
295
+ - Rollback to ci path changes (#161) ([8113568](https://github.com/NanoForge-dev/cli/commit/81135687d625712fc8ee2e656bdc7da157048f40)) by @Exeloo
296
+
297
+ # [@nanoforge-dev/cli@1.5.2](https://github.com/NanoForge-dev/cli/compare/@nanoforge-dev/cli@1.4.2...@nanoforge-dev/cli@1.5.2) - (2026-06-04)
298
+
299
+ ## Bug Fixes
300
+
301
+ - Change local bun path finding (#144) ([76be5df](https://github.com/NanoForge-dev/cli/commit/76be5df8810c3589b16c75b18d95262c887aee68)) by @Exeloo
302
+ - **docs:** Sumary link bad format (#140) ([dbea2cf](https://github.com/NanoForge-dev/cli/commit/dbea2cf411cfc8c1b60d0abd62d51d1631e3a2ee)) by @Tchips46
303
+ - Add git remote and docker params handling (#130) ([99fbe2b](https://github.com/NanoForge-dev/cli/commit/99fbe2b1a5af9541650732314127413829b4192e)) by @Exeloo
304
+
305
+ ## Documentation
306
+
307
+ - Refactor docs to mdx (#134) ([d301d90](https://github.com/NanoForge-dev/cli/commit/d301d9069fdb8d582ecc14ad2e0f5d91b4deb40f)) by @MartinFillon
308
+
309
+ ## Features
310
+
311
+ - Handle lib deps (#131) ([9093c02](https://github.com/NanoForge-dev/cli/commit/9093c0207b4448eee8395885c9b7740ae8700307)) by @Exeloo
312
+
313
+ # [@nanoforge-dev/cli@1.4.2](https://github.com/NanoForge-dev/cli/compare/@nanoforge-dev/cli@1.4.1...@nanoforge-dev/cli@1.4.2) - (2026-04-19)
314
+
315
+ ## Bug Fixes
316
+
317
+ - Env nanoforge url (#127) ([bf23728](https://github.com/NanoForge-dev/cli/commit/bf237286ea9cfc259b782084091b6c1d1f3535a9)) by @Exeloo
318
+
319
+ # [@nanoforge-dev/cli@1.4.1](https://github.com/NanoForge-dev/cli/compare/@nanoforge-dev/cli@1.4.0...@nanoforge-dev/cli@1.4.1) - (2026-04-19)
320
+
321
+ ## Features
322
+
323
+ - Add git init on new command (#122) ([921a182](https://github.com/NanoForge-dev/cli/commit/921a182148ddfbf8470be1518cd8cbcb6092c7fb)) by @Exeloo
324
+ - Add editor command (#118) ([918da39](https://github.com/NanoForge-dev/cli/commit/918da39ce41e421a5a3ae6c4d8264dbeed012209)) by @Exeloo
325
+
326
+ # [@nanoforge-dev/cli@1.4.0](https://github.com/NanoForge-dev/cli/compare/@nanoforge-dev/cli@1.3.0...@nanoforge-dev/cli@1.4.0) - (2026-04-10)
327
+
328
+ ## Features
329
+
330
+ - Add static folder to build (#114) ([e6e4e36](https://github.com/NanoForge-dev/cli/commit/e6e4e36f06cc146de76df7f4806d7f33a815382b)) by @Exeloo
331
+ - Add create command (#111) ([3470dc6](https://github.com/NanoForge-dev/cli/commit/3470dc6e235e26b1b3fa0d5fabd6b855c18aed88)) by @Exeloo
332
+ - Add editor flag on code generation (#106) ([bd3ce28](https://github.com/NanoForge-dev/cli/commit/bd3ce28bcaa72c72de34783b19951a181d39cf46)) by @Exeloo
333
+ - **stop:** Catch signals end repeat it to childs (#105) ([812333d](https://github.com/NanoForge-dev/cli/commit/812333d2dff2ad365e780d75f07ee7eb72942174)) by @Tchips46
334
+
335
+ ### New Contributors
336
+
337
+ - @Tchips46 made their first contribution in #105
338
+
339
+ # [@nanoforge-dev/cli@1.3.0](https://github.com/NanoForge-dev/cli/compare/@nanoforge-dev/cli@1.2.0...@nanoforge-dev/cli@1.3.0) - (2026-03-15)
340
+
341
+ ## Bug Fixes
342
+
343
+ - Npm exec issues and add lint param to new command (#101) ([a1ed759](https://github.com/NanoForge-dev/cli/commit/a1ed75977348cac78f1adb825acea465d9ebe69a)) by @Exeloo
344
+
345
+ ## Features
346
+
347
+ - Add components and systems installation (#98) ([5fca64a](https://github.com/NanoForge-dev/cli/commit/5fca64a86219beec9b4b5b72c576d973dc012937)) by @Exeloo
348
+ - Add publish and unpublish commands (#97) ([e49d00d](https://github.com/NanoForge-dev/cli/commit/e49d00d50584e0170d3e0793dd6d6e265939b519)) by @Exeloo
349
+ - Add env handling in start command (#96) ([c61f8f0](https://github.com/NanoForge-dev/cli/commit/c61f8f0151b8bfd8be74d44f426d9b9e2978ac4b)) by @Exeloo
350
+ - Add login and logout commands with apiKey handling (#88) ([5be790a](https://github.com/NanoForge-dev/cli/commit/5be790a0441cf1cebe60c6cd919a964a82a4e0a6)) by @Exeloo
351
+
352
+ # [@nanoforge-dev/cli@1.2.0](https://github.com/NanoForge-dev/cli/compare/@nanoforge-dev/cli@1.1.1...@nanoforge-dev/cli@1.2.0) - (2026-03-04)
353
+
354
+ ## Bug Fixes
355
+
356
+ - Add name to cwd to install packages in new (#69) ([1e17868](https://github.com/NanoForge-dev/cli/commit/1e17868398e6ec0f639e83f23db6d0af8a8673af)) by @Exeloo
357
+
358
+ ## Features
359
+
360
+ - **docker:** Setup new docker option to generete docker file (#82) ([99244b1](https://github.com/NanoForge-dev/cli/commit/99244b1ffc225ffb55d85f85a9a1eeddb87de628)) by @MartinFillon
361
+
362
+ ## Refactor
363
+
364
+ - Beautify all code base and add tests (#77) ([67c297c](https://github.com/NanoForge-dev/cli/commit/67c297c191c1251a2776d2c3caf0cbd8ff36f906)) by @Exeloo
365
+
366
+ ### New Contributors
367
+
368
+ - @dependabot[bot] made their first contribution in #71
369
+
370
+ # [1.1.1](https://github.com/NanoForge-dev/cli/compare/1.0.0...1.1.1) - (2026-02-18)
371
+
372
+ ## Bug Fixes
373
+
374
+ - Change exec command (#66) ([5fe368c](https://github.com/NanoForge-dev/cli/commit/5fe368cc92ac1a12cdbe3f05248f8f3ae4dc38b1)) by @Exeloo
375
+ - Resolve boolean issue on schematics (#65) ([2acb95d](https://github.com/NanoForge-dev/cli/commit/2acb95d8c2388ec121d68a039f96a8d04108cb23)) by @Exeloo
376
+ - Add binary resolution for bun (#63) ([b874e5e](https://github.com/NanoForge-dev/cli/commit/b874e5e2d6107a3fa8f939749dc486dded1f3adf)) by @Exeloo
377
+
378
+ ## Documentation
379
+
380
+ - Fix documentation (#45) ([11490ca](https://github.com/NanoForge-dev/cli/commit/11490caa23fc3cf7f0f09e0dd3be1d6db559338e)) by @Exeloo
381
+
382
+ ## Features
383
+
384
+ - **https:** Setup certificate passing (#75) ([fc00b02](https://github.com/NanoForge-dev/cli/commit/fc00b02b2ae96523bf01e675e50b751b576b3e58)) by @MartinFillon
385
+ - Add docker release and local bun (#49) ([f3e2ad6](https://github.com/NanoForge-dev/cli/commit/f3e2ad6096d2c12ca17e191290d460fc74cc5839)) by @Exeloo
386
+ - Add watch and `dev` command (#46) ([7b8413c](https://github.com/NanoForge-dev/cli/commit/7b8413c8125bd1763bd94dd8710fa6130e560cbc)) by @Exeloo
387
+
388
+ ## Testing
389
+
390
+ - Add unit and e2e tests (#67) ([2ef8f9d](https://github.com/NanoForge-dev/cli/commit/2ef8f9d47db96d8a468564dd0b36e3d30121f646)) by @Exeloo
391
+
392
+ ### New Contributors
393
+
394
+ - @github-actions[bot] made their first contribution in #59
395
+
396
+ # [1.1.0](https://github.com/NanoForge-dev/cli/compare/1.0.0...1.1.0) - (2026-02-09)
397
+
398
+ ## Documentation
399
+
400
+ - Fix documentation (#45) ([11490ca](https://github.com/NanoForge-dev/cli/commit/11490caa23fc3cf7f0f09e0dd3be1d6db559338e)) by @Exeloo
401
+
402
+ ## Features
403
+
404
+ - Add docker release and local bun (#49) ([f3e2ad6](https://github.com/NanoForge-dev/cli/commit/f3e2ad6096d2c12ca17e191290d460fc74cc5839)) by @Exeloo
405
+ - Add watch and `dev` command (#46) ([7b8413c](https://github.com/NanoForge-dev/cli/commit/7b8413c8125bd1763bd94dd8710fa6130e560cbc)) by @Exeloo
406
+
407
+ # [1.0.0](https://github.com/NanoForge-dev/cli/tree/1.0.0) - (2026-01-06)
408
+
409
+ ## Bug Fixes
410
+
411
+ - Change bun binary (#34) ([c529b33](https://github.com/NanoForge-dev/cli/commit/c529b332f0039ccb29c3f1a350498f057dc7f106)) by @Exeloo
412
+
413
+ ## Documentation
414
+
415
+ - Write-usage-and-complete-schemas (#36) ([2f4dd3a](https://github.com/NanoForge-dev/cli/commit/2f4dd3ac21e623565dc48f0c2a70279db9916312)) by @MartinFillon
416
+ - Add contributing docs and actions (#33) ([55341d1](https://github.com/NanoForge-dev/cli/commit/55341d1329076d80db1429c607c1f3cf52d2b4d8)) by @Exeloo
417
+ - Setup action to push all docs to docs repo (#29) ([99e26c6](https://github.com/NanoForge-dev/cli/commit/99e26c6feed162502ddee28d5de2f1451ee55c74)) by @MartinFillon
418
+
419
+ ## Features
420
+
421
+ - Split ecs and add miscellaneous (#28) ([35175e0](https://github.com/NanoForge-dev/cli/commit/35175e05bb511fa0634dac52f9b8b45acaeccb34)) by @Exeloo
422
+ - Add options on `new` command (#27) ([09988c2](https://github.com/NanoForge-dev/cli/commit/09988c2890818fc360c16a2632b8f00a9f14c816)) by @Exeloo
423
+ - Add `generate` command (#26) ([dc35464](https://github.com/NanoForge-dev/cli/commit/dc3546472474dcaa016d03750486be5cc17a6d96)) by @Exeloo
424
+ - Enhance `new` command with client and server contents (#22) ([aec2d20](https://github.com/NanoForge-dev/cli/commit/aec2d203e9131317239380e72eff45a6eb83c0e4)) by @Exeloo
425
+ - Add `new` command (#15) ([f9e3145](https://github.com/NanoForge-dev/cli/commit/f9e3145c8aa965571a4de87b27f4a7c700d3a86f)) by @Exeloo
426
+ - Add `run` command (#14) ([734615e](https://github.com/NanoForge-dev/cli/commit/734615efad12199a8e87e9b96c46945ba54f1e28)) by @Exeloo
427
+ - Add build command (#10) ([62ba12a](https://github.com/NanoForge-dev/cli/commit/62ba12ad5249d8fbade7430ee3fbe5b500586e26)) by @Exeloo
428
+ - Add install command ([d1cf961](https://github.com/NanoForge-dev/cli/commit/d1cf961d2e0ed9cfeb735df4d00de33a41ae8048)) by @Exeloo
429
+ - Add base cli ([5408c9f](https://github.com/NanoForge-dev/cli/commit/5408c9f26c27885c8bfd61c56da5655477a433a4)) by @Exeloo
430
+ - Init repo ([d5ef49d](https://github.com/NanoForge-dev/cli/commit/d5ef49d20cf812fe9e19e18e1a31cb95fc522b14)) by @Exeloo
431
+
432
+ ### New Contributors
433
+
434
+ - @MartinFillon made their first contribution in #36
435
+ - @Exeloo made their first contribution in #34
436
+ - @renovate[bot] made their first contribution in #19
package/README.md CHANGED
@@ -8,7 +8,7 @@
8
8
  <a href="https://www.npmjs.com/package/@nanoforge-dev/cli"><img src="https://img.shields.io/npm/v/@nanoforge-dev/cli.svg?maxAge=3600" alt="npm version" /></a>
9
9
  <a href="https://www.npmjs.com/package/@nanoforge-dev/cli"><img src="https://img.shields.io/npm/dt/@nanoforge-dev/cli.svg?maxAge=3600" alt="npm downloads" /></a>
10
10
  <a href="https://github.com/NanoForge-dev/CLI/actions/workflows/tests.yml"><img src="https://github.com/NanoForge-dev/CLI/actions/workflows/tests.yml/badge.svg" alt="Tests status" /></a>
11
- <a href="https://github.com/NanoForge-dev/CLI/actions/workflows/push-docs.yml"><img src="https://github.com/NanoForge-dev/CLI/actions/workflows/push-docs.yml/badge.svg" alt="Documentation status" /></a>
11
+ <a href="https://github.com/NanoForge-dev/CLI/actions/workflows/release.yml"><img src="https://github.com/NanoForge-dev/CLI/actions/workflows/release.yml/badge.svg" alt="Release status" /></a>
12
12
  <a href="https://github.com/NanoForge-dev/CLI/commits/main"><img src="https://img.shields.io/github/last-commit/NanoForge-dev/CLI.svg?logo=github&logoColor=ffffff" alt="Last commit" /></a>
13
13
  <a href="https://github.com/NanoForge-dev/CLI/graphs/contributors"><img src="https://img.shields.io/github/contributors/NanoForge-dev/CLI.svg?maxAge=3600&logo=github&logoColor=fff&color=00c7be" alt="Contributors" /></a>
14
14
  </p>
@@ -78,7 +78,6 @@ Used to run your nanoforge project in dev mode.
78
78
 
79
79
  - `-d, --directory <directory>` specify the working directory of the command.
80
80
  - `-c, --config <config>` path to the config file.
81
- - `--generate` generate app files from config, like generate command in dev mode. (default: `false`)
82
81
 
83
82
  ### `editor`
84
83
 
@@ -89,15 +88,6 @@ Used to start the nanoforge editor.
89
88
  - `--open` open the editor in the default web browser (default: `true` if path is specified, `false` otherwise).
90
89
  - `--no-open` do not open the editor in the default web browser.
91
90
 
92
- ### `generate`
93
-
94
- Used to generate nanoforge project files from config.
95
-
96
- - `-d, --directory <directory>` specify the working directory of the command.
97
- - `-c, --config <config>` path to the config file.
98
- - `--editor` generate the editor main file.
99
- - `--watch` generate app in watching mode. (default: `false`)
100
-
101
91
  ### `install` or `add`
102
92
 
103
93
  Used to add nanoforge components, systems or libraries to your project.
@@ -164,8 +154,8 @@ Used to start your nanoforge project.
164
154
  - `--client-dir <clientDirectory>` specify the directory of the client.
165
155
  - `--server-dir <serverDirectory>` specify the directory of the server.
166
156
  - `--watch` run app in watching mode. (default: `false`)
167
- - `--cert <cert>` path to the SSL certificate for HTTPS.
168
- - `--key <key>` path to the SSL key for HTTPS.
157
+ - `--cert <cert>` path to the TLS certificate for HTTPS.
158
+ - `--key <key>` path to the TLS key for HTTPS.
169
159
 
170
160
  ### `unpublish`
171
161
 
@@ -193,7 +183,7 @@ Variables are scoped by prefix:
193
183
 
194
184
  > **Note:** Prefixes are stripped before the variable is exposed to libraries.
195
185
 
196
- For full documentation on how libraries consume these variables, see [@nanoforge-dev/config](https://github.com/NanoForge-dev/Engine/tree/main/packages/config).
186
+ For full documentation on how libraries consume these variables, see [@nanoforge-dev/config](https://github.com/NanoForge-dev/CLI/tree/main/libs/config).
197
187
 
198
188
  ## Contributing
199
189
 
@@ -1,10 +1,8 @@
1
1
  import { Command } from "commander";
2
-
3
2
  //#region src/command/command.loader.d.ts
4
- declare class CommandLoader {
3
+ export declare class CommandLoader {
5
4
  static load(program: Command): Promise<void>;
6
5
  private static handleInvalidCommand;
7
6
  }
8
7
  //#endregion
9
- export { CommandLoader };
10
8
  //# sourceMappingURL=command.loader.d.ts.map
@@ -1 +1 @@
1
- {"version":3,"file":"command.loader.d.ts","names":[],"sources":["../src/command/command.loader.ts"],"mappings":";;;cAiCa,aAAA;EAAA,OACS,IAAA,CAAK,OAAA,EAAS,OAAA,GAAU,OAAO;EAAA,eAgBpC,oBAAA;AAAA"}
1
+ {"version":3,"file":"command.loader.d.ts","names":[],"sources":["../src/command/command.loader.ts"],"mappings":";;qBA+Ba;SACS,KAAK,SAAS,UAAU;iBAe7B"}