@oddington/cli 0.1.78 → 0.1.80

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.
Files changed (3) hide show
  1. package/README.md +53 -0
  2. package/dist/os.js +434 -370
  3. package/package.json +2 -2
package/README.md CHANGED
@@ -41,6 +41,13 @@ Run `os --help` or add `--help` to any command for the full command list.
41
41
  Commands print readable output by default. Add `--json` when another program
42
42
  will consume the result.
43
43
 
44
+ `os app dev <name>` shows recent development-server output in your terminal if
45
+ startup fails or the server later stops. It distinguishes an exit from a startup
46
+ timeout and includes the app's retry command. This is output from your local dev
47
+ script; OS keeps only a bounded tail in memory and does not save or upload it.
48
+ Successful startup stays quiet apart from OS progress, and Vite handles ordinary
49
+ compilation errors through its browser overlay while you edit.
50
+
44
51
  Dropbox connection setup uses an offline OAuth URL and hidden one-time code entry:
45
52
 
46
53
  ```sh
@@ -147,6 +154,20 @@ The shared declaration contains no package import. The worktree root needs no
147
154
  package installation; each consuming project keeps its own compatible
148
155
  `@oddington/sdk` dependency.
149
156
 
157
+ For unpublished schema changes in this checkout, run:
158
+
159
+ ```sh
160
+ os data schema general --local
161
+ ```
162
+
163
+ This reads only `_schema.yaml` files beneath `general/`, including uncommitted
164
+ and untracked schemas. It needs no login, network, remote or named branch.
165
+ It updates the same generated file and TypeScript settings and preserves other
166
+ repository aliases. The command reports whether it used local or published
167
+ schemas. Invalid local schemas stop generation without replacing your existing
168
+ types; there is no fallback to published schemas. Run it again after changing a
169
+ local schema. App development does not automatically regenerate types.
170
+
150
171
  Keep importing `data` from `@oddington/sdk`. A known repository literal now gains
151
172
  schema-aware `records.query`, `pages` and `all` queries and projected values.
152
173
  No source import, app declaration, build or launch is needed. Other operations
@@ -187,6 +208,38 @@ origin alive while HMR updates the interface. There is no production build on
187
208
  this path. Install development dependencies first. App declaration and routine
188
209
  definition changes require a restart; normal interface edits do not.
189
210
 
211
+ For ordinary app development, that command uses your installed CLI and the app's
212
+ installed SDK. To test unreleased OS changes, first build the CLI and SDK in the
213
+ OS checkout:
214
+
215
+ ```sh
216
+ cd /path/to/os
217
+ bun run --filter @oddington/cli build
218
+ ```
219
+
220
+ Then run from the customer repository:
221
+
222
+ ```sh
223
+ os app dev billing --local-os /path/to/os
224
+ ```
225
+
226
+ This explicitly runs that checkout's built CLI and supplies its built browser
227
+ SDK to the app's Vite server. Both selected paths are shown on stderr. Missing
228
+ builds stop with build guidance; no package is installed or substituted. The
229
+ app's existing Vite config/plugins still run. A temporary config override and
230
+ separate dependency cache last only for this invocation; customer dependencies,
231
+ lockfiles and authored config are preserved. Existing login and backend services
232
+ are used normally. Interface edits keep HMR; OS CLI/SDK edits require rebuilding
233
+ OS and restarting this command. Stop and omit `--local-os` to return to ordinary
234
+ installed packages. This flag selects local packages, not a local backend.
235
+
236
+ Until your installed CLI supports this option, invoke the built CLI directly
237
+ from the customer repository:
238
+
239
+ ```sh
240
+ node /path/to/os/apps/cli/dist/os.js app dev billing --local-os /path/to/os
241
+ ```
242
+
190
243
  Both commands print a clean local address you can open in multiple browsers
191
244
  simultaneously, including a chat browser that can reach this machine. Starting
192
245
  the host trusts this workstation's loopback, including other local processes