@nanoforge-dev/cli 2.3.1 → 3.0.2

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 CHANGED
@@ -2,6 +2,53 @@
2
2
 
3
3
  All notable changes to this project will be documented in this file.
4
4
 
5
+ # [3.0.2](https://github.com/NanoForge-dev/CLI/compare/3.0.1...3.0.2) - (2026-11-20)
6
+
7
+ ## Bug Fixes
8
+
9
+ - **cli:** Import the local cli command loader through a file url (#272) ([1a5eec5](https://github.com/NanoForge-dev/CLI/commit/1a5eec5c00a0e52bf6655ed639196240fad9111b)) by @Exeloo
10
+ - **cli:** Make nf and its tests work on windows (#274) ([cf32f31](https://github.com/NanoForge-dev/CLI/commit/cf32f310945f8abd4ec1f3557f8e67e33df3920d)) by @Exeloo
11
+ - **schematics:** Import the ecs types from @nanoforge-dev/ecs in item templates (#271) ([e95b881](https://github.com/NanoForge-dev/CLI/commit/e95b881767113eae330d33b174086fe80461b9e9)) by @Exeloo
12
+
13
+ # [3.0.1](https://github.com/NanoForge-dev/CLI/compare/3.0.0...3.0.1) - (2026-11-08)
14
+
15
+ ## Bug Fixes
16
+
17
+ - **cli:** Run commands without a shell and keep the local api key private (#268) ([bdbe963](https://github.com/NanoForge-dev/CLI/commit/bdbe963096b9a80f4910996dc04b8c7d0d41d8f9)) by @Exeloo
18
+
19
+ # [3.0.0](https://github.com/NanoForge-dev/CLI/compare/2.3.1...3.0.0) - (2026-11-08)
20
+
21
+ ## Breaking Changes
22
+
23
+ - **cli:** Install, publish and unpublish on the shared registry lib (#263) ([9fb3abf](https://github.com/NanoForge-dev/CLI/commit/9fb3abfc4ff9c8630acb7a559be3129da04af221)) by @Exeloo
24
+ - **BREAKING CHANGE:** nf install drops --server, and installs into nf_modules instead of copying files into client/ or server/. Manifests must use the registry format (@scope/name, version, type package or plugin): publish.paths and the scope/name format are no longer read.
25
+
26
+ ## Bug Fixes
27
+
28
+ - **registry:** Keep every request on the registry's origin (#264) ([2ac2f42](https://github.com/NanoForge-dev/CLI/commit/2ac2f424027fac18a6951513dc401990f63f252b)) by @Exeloo
29
+ - **nightly:** Build workspace packages and ensure schematics collection exists before e2e (#257) ([b98ef13](https://github.com/NanoForge-dev/CLI/commit/b98ef1393b6a994c113a8dd9952f6fb34d316be8)) by @MartinFillon
30
+ - **schematics:** Resolve and quote paths correctly on Windows (#240) ([6928a8c](https://github.com/NanoForge-dev/CLI/commit/6928a8c63d8fa492e5fe64eb321cdb8e8d34dc8d)) by @Raphael-Mabille
31
+
32
+ ## Documentation
33
+
34
+ - Add agents documentation and skill (#243) ([eebe5e1](https://github.com/NanoForge-dev/CLI/commit/eebe5e13b86e3c7e7d43a18550f98eadfdb8e850)) by @hvrp3r
35
+ - Rewrite the cli pages and guides against the current code (#255) ([d71a47c](https://github.com/NanoForge-dev/CLI/commit/d71a47c8e332829e9a403d153e796b176d31cb6b)) by @Exeloo
36
+ - Drop number prefixes from page names and add an explicit navigation (#253) ([42d0e87](https://github.com/NanoForge-dev/CLI/commit/42d0e87997756e3f8af4b569799a066416209cfc)) by @Exeloo
37
+
38
+ ## Features
39
+
40
+ - New CLI options for AGENTS.md documentation (#245) ([63a1446](https://github.com/NanoForge-dev/CLI/commit/63a144662840e3d7487b18f34feade8230507831)) by @hvrp3r
41
+ - **nightly:** Setup nightly test runner script (#251) ([98d5e78](https://github.com/NanoForge-dev/CLI/commit/98d5e780429d1d0a078b1adc1e76b70c865aebb9)) by @MartinFillon
42
+ - Add theme plugin (#248) ([e62ec83](https://github.com/NanoForge-dev/CLI/commit/e62ec831e5a87d5221401a3382856738985a507a)) by @Exeloo
43
+ - **build:** Build the server app for the browser in p2p workspaces (#246) ([ab74db7](https://github.com/NanoForge-dev/CLI/commit/ab74db74b93f7b6035cd278f52ba46f9d6b7367d)) by @Tchips46
44
+ - **schematics:** Add support for generating NanoForge editor plugins (#241) ([0440154](https://github.com/NanoForge-dev/CLI/commit/044015451885e5ef2a3ad6475477ae326fc21406)) by @Exeloo
45
+ - **editor:** Add support for custom port and project paths via CLI options (#242) ([d792dbb](https://github.com/NanoForge-dev/CLI/commit/d792dbb177095f715bb90092ce6ba14e8c4478eb)) by @Exeloo
46
+
47
+ ### New Contributors
48
+
49
+ - @hvrp3r made their first contribution in #245
50
+ - @Raphael-Mabille made their first contribution in #240
51
+
5
52
  # [2.3.1](https://github.com/NanoForge-dev/CLI/compare/2.3.0...2.3.1) - (2026-09-25)
6
53
 
7
54
  # [2.3.0](https://github.com/NanoForge-dev/CLI/compare/1.6.2...2.3.0) - (2026-09-24)
package/README.md CHANGED
@@ -65,7 +65,16 @@ Used to build your nanoforge project.
65
65
 
66
66
  Used to create nanoforge components or systems.
67
67
 
68
- - `<type>` the type to create (component or system).
68
+ `nf create plugin` creates an **editor plugin** instead: a small working plugin (a panel, a command, a setting, an undoable action) in a folder of its own. It needs no project around it.
69
+
70
+ ```sh
71
+ nf create plugin --name @acme/counter # writes ./counter
72
+ nf create plugin --name @acme/forest --template theme # a color theme, no code
73
+ ```
74
+
75
+ `--name` is the plugin's registry name (`@scope/name`), and `--path` the folder to write (default: the name without its scope). The new folder's README says how to run it in the editor.
76
+
77
+ - `<type>` the type to create (component, system or plugin).
69
78
  - `-d, --directory <directory>` specify the working directory of the command.
70
79
  - `-c, --config <config>` path to the config file.
71
80
  - `-n, --name <name>` name of the component/system.
@@ -90,12 +99,11 @@ Used to start the nanoforge editor.
90
99
 
91
100
  ### `install` or `add`
92
101
 
93
- Used to add nanoforge components, systems or libraries to your project.
102
+ Used to add NanoForge registry packages, or npm libraries, to your project.
94
103
 
95
- - `[names...]` names of the components/systems/libraries to install.
104
+ - `[names...]` registry packages to install into `nf_modules`, `@scope/name` or `@scope/name@<range>` (npm names with `--lib`). Without names, installs what `nanoforge.packages.lock.json` lists.
96
105
  - `-d, --directory <directory>` specify the working directory of the command.
97
- - `-l, --lib` install a library instead of a component/system. (default: `false`)
98
- - `-s, --server` install on server instead of client. (default: `false`)
106
+ - `-l, --lib` install npm libraries with the package manager instead. (default: `false`)
99
107
 
100
108
  ### `login`
101
109
 
@@ -132,6 +140,7 @@ Used to create a new nanoforge project.
132
140
  - `--docker` generate docker files.
133
141
  - `--no-docker` do not generate docker files.
134
142
  - `--no-lint` do not generate lint files.
143
+ - `--no-agents` do not generate the `AGENTS.md` and `CLAUDE.md` files for AI coding agents.
135
144
  - `--editor` add editor dependencies.
136
145
  - `--git` generate a git repository.
137
146
  - `--no-git` do not generate a git repository.
@@ -140,9 +149,10 @@ Used to create a new nanoforge project.
140
149
 
141
150
  ### `publish`
142
151
 
143
- Used to publish a package to the Nanoforge registry.
152
+ Used to publish a package to the NanoForge registry: zips what its `nanoforge.manifest.json` names (its `contents` paths, sub-manifests, readme, a plugin's build output next to its entry, and the root's `README*`, `LICENSE*` and `CHANGELOG*`), without secrets such as `.env*`, `.npmrc`, `.nanoforgerc`, credentials and keys, nor `.git`, `node_modules` and `nf_modules`, lists the packed files, and publishes it as the manifest's version.
144
153
 
145
154
  - `-d, --directory <directory>` specify the working directory of the command.
155
+ - `--dry-run` list the files to publish, and publish nothing. (default: `false`)
146
156
 
147
157
  ### `start`
148
158
 
@@ -159,7 +169,7 @@ Used to start your nanoforge project.
159
169
 
160
170
  ### `unpublish`
161
171
 
162
- Used to unpublish a package from the Nanoforge registry.
172
+ Used to unpublish the version named in `nanoforge.manifest.json` from the NanoForge registry.
163
173
 
164
174
  - `-d, --directory <directory>` specify the working directory of the command.
165
175
 
@@ -1,8 +1,6 @@
1
1
  import { Command } from "commander";
2
- //#region src/command/command.loader.d.ts
3
2
  export declare class CommandLoader {
4
3
  static load(program: Command): Promise<void>;
5
4
  private static handleInvalidCommand;
6
5
  }
7
- //#endregion
8
6
  //# sourceMappingURL=command.loader.d.ts.map
@@ -1 +1 @@
1
- {"version":3,"file":"command.loader.d.ts","names":[],"sources":["../src/command/command.loader.ts"],"mappings":";;qBA+Ba;SACS,KAAK,SAAS,UAAU;iBAe7B"}
1
+ {"version":3,"file":"command.loader.d.ts","names":[],"sources":["../src/command/command.loader.ts"],"mappings":";qBA+Ba;SACS,KAAK,SAAS,UAAU;iBAe7B"}