flowdular 0.5.1 → 0.6.1
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/README.md +14 -8
- package/dist/distribution.js +395 -952
- package/dist/index.js +7004 -4212
- package/package.json +2 -2
package/README.md
CHANGED
|
@@ -33,8 +33,10 @@ The executable is `flowdular`; `fd` is also available as an alias. Run commands
|
|
|
33
33
|
| ----------------------------------------- | ----------------------------------------------- |
|
|
34
34
|
| `pnpm flowdular doctor` | Inspect workspace configuration and diagnostics |
|
|
35
35
|
| `pnpm flowdular help` | List commands and supported flags |
|
|
36
|
-
| `pnpm flowdular module
|
|
37
|
-
| `pnpm flowdular module
|
|
36
|
+
| `pnpm flowdular module source add` | Configure a catalog, Git or local source |
|
|
37
|
+
| `pnpm flowdular module search` | Browse a configured source |
|
|
38
|
+
| `pnpm flowdular module plan <id>` | Save a pinned installation plan |
|
|
39
|
+
| `pnpm flowdular module apply <plan-id>` | Install exact source from that plan |
|
|
38
40
|
| `pnpm flowdular module sync --apply` | Regenerate application composition |
|
|
39
41
|
| `pnpm flowdular module validate --locked` | Validate modules against the installation lock |
|
|
40
42
|
|
|
@@ -43,11 +45,15 @@ The executable is `flowdular`; `fd` is also available as an alias. Run commands
|
|
|
43
45
|
For a catalog containing `expenses.core`:
|
|
44
46
|
|
|
45
47
|
```sh
|
|
46
|
-
#
|
|
47
|
-
pnpm flowdular module
|
|
48
|
+
# Configure a source once.
|
|
49
|
+
pnpm flowdular module source add team ./registry/index.json --apply
|
|
48
50
|
|
|
49
|
-
#
|
|
50
|
-
pnpm flowdular module
|
|
51
|
+
# Save and inspect the exact dependency, permission and migration plan.
|
|
52
|
+
pnpm flowdular module plan expenses.core --source team --apply
|
|
53
|
+
pnpm flowdular module plan show <plan-id>
|
|
54
|
+
|
|
55
|
+
# Install only the pinned release in that plan.
|
|
56
|
+
pnpm flowdular module apply <plan-id> --apply
|
|
51
57
|
|
|
52
58
|
# Enable the module and grant its scopes in the configured application.
|
|
53
59
|
pnpm flowdular module enable expenses.core --apply
|
|
@@ -56,9 +62,9 @@ pnpm flowdular module enable expenses.core --apply
|
|
|
56
62
|
pnpm flowdular module validate --locked
|
|
57
63
|
```
|
|
58
64
|
|
|
59
|
-
|
|
65
|
+
Planning and installation preview by default. Applying a plan writes source under `modules/`; activation is a separate step. Enabling a module updates application composition and can grant scopes against the configured database.
|
|
60
66
|
|
|
61
|
-
|
|
67
|
+
Use a local or HTTPS catalog, or a Git source pinned to a full commit. See the [Module Studio guide](https://github.com/Flowdular/flowdular/blob/main/docs/module-distribution.md) for commands and trust rules.
|
|
62
68
|
|
|
63
69
|
## Automation
|
|
64
70
|
|