@object-ui/cli 17.5.0 → 17.7.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 +2376 -0
- package/README.md +15 -24
- package/dist/{chunk-2MZA766D.js → chunk-VMMIGYU3.js} +390 -151
- package/dist/chunk-VMMIGYU3.js.map +1 -0
- package/dist/cli.js +1161 -582
- package/dist/cli.js.map +1 -1
- package/dist/index.d.ts +2 -0
- package/dist/index.js +1 -1
- package/package.json +9 -7
- package/dist/chunk-2MZA766D.js.map +0 -1
package/README.md
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
# @object-ui/cli
|
|
2
2
|
|
|
3
|
-
> Standalone CLI for **Object UI** — scaffold, develop, build
|
|
3
|
+
> Standalone CLI for **Object UI** — scaffold, develop, build and validate
|
|
4
4
|
> JSON/YAML schema-driven applications.
|
|
5
5
|
|
|
6
6
|
```bash
|
|
@@ -49,6 +49,12 @@ objectui dev --no-open
|
|
|
49
49
|
- `-h, --host <host>` — default `localhost`
|
|
50
50
|
- `--no-open` — do not open browser
|
|
51
51
|
|
|
52
|
+
`dev`, `serve` and `build` locate the project the same way: a `pages/` directory
|
|
53
|
+
beside the schema argument means file-system routing (with that file as the app
|
|
54
|
+
config), otherwise a `pages/` directory in the current directory, otherwise the
|
|
55
|
+
named file is rendered on its own. So `objectui build my-app/app.json` from above
|
|
56
|
+
`my-app/` builds the same routes `objectui dev my-app/app.json` serves.
|
|
57
|
+
|
|
52
58
|
### `objectui build [schema]`
|
|
53
59
|
|
|
54
60
|
Build the application for production.
|
|
@@ -81,37 +87,22 @@ objectui start --port 8080 --dir build
|
|
|
81
87
|
|
|
82
88
|
Legacy alias of `dev` (kept for older scripts).
|
|
83
89
|
|
|
84
|
-
### `objectui lint`
|
|
85
|
-
|
|
86
|
-
Lint the generated application code via ESLint.
|
|
87
|
-
|
|
88
|
-
```bash
|
|
89
|
-
objectui lint --fix
|
|
90
|
-
```
|
|
91
|
-
|
|
92
|
-
### `objectui test`
|
|
93
|
-
|
|
94
|
-
Run the application's tests via Vitest.
|
|
95
|
-
|
|
96
|
-
```bash
|
|
97
|
-
objectui test --watch
|
|
98
|
-
objectui test --coverage
|
|
99
|
-
objectui test --ui
|
|
100
|
-
```
|
|
101
|
-
|
|
102
90
|
### `objectui generate <type> <name>` (alias `g`)
|
|
103
91
|
|
|
104
92
|
Generate new resources (`resource`/`object`, `page`, `plugin`).
|
|
105
93
|
|
|
106
|
-
### `objectui add <component>`
|
|
107
|
-
|
|
108
|
-
Add a new component renderer to your project.
|
|
109
|
-
|
|
110
94
|
### `objectui validate [schema]`
|
|
111
95
|
|
|
112
96
|
Validate a schema file against the ObjectUI specification.
|
|
113
97
|
|
|
114
|
-
|
|
98
|
+
A failure is reported at the document root and then narrowed to the union arm
|
|
99
|
+
your `type` selected — the `1.1`-style entries under a numbered issue are that
|
|
100
|
+
arm's own diagnosis, at the real path of the node that failed. When no component
|
|
101
|
+
type matches, the report names the nearest few of the accepted values instead of
|
|
102
|
+
listing all of them. See the
|
|
103
|
+
[docs](https://www.objectui.org/docs/utilities/cli) for worked output.
|
|
104
|
+
|
|
105
|
+
### `objectui check`, `objectui doctor`, `objectui analyze`
|
|
115
106
|
|
|
116
107
|
Utility commands — see `objectui --help`.
|
|
117
108
|
|