heximon 0.26.0 → 0.28.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/README.md +16 -0
- package/dist/bin.mjs +1902 -1625
- package/dist/index.d.mts +47 -0
- package/dist/index.mjs +1 -1
- package/dist/{skills-command-Czsv_c74.mjs → skills-command-BiuBtTbZ.mjs} +6 -1
- package/package.json +18 -17
package/README.md
CHANGED
|
@@ -187,6 +187,16 @@ the fix instructions plus a non-zero exit code.
|
|
|
187
187
|
prints where. This applies to an app. In a published module package, `--emit` and `debug: true` write
|
|
188
188
|
nothing, and the pretty output prints a notice (`--json` omits the notice and `emittedTo`). `vp pack` regenerates the `create<Module>` factory in
|
|
189
189
|
`.heximon/library/`.
|
|
190
|
+
- **`heximon check` compiles a Nuxt or Nitro app for the target of its Nitro preset.** The build takes the
|
|
191
|
+
deploy target from the preset, so the check does too, and so do `heximon graph`, `heximon workflows` and
|
|
192
|
+
`heximon routes`. A Nitro app gives the preset in the text of its config files or in `NITRO_PRESET`, and the
|
|
193
|
+
Nitro of the app resolves the name as the build does (with no preset, it detects the provider, such as
|
|
194
|
+
`CF_PAGES=1`). The check never loads a custom preset (a path or a package), so it cannot read its target. A
|
|
195
|
+
Nuxt app gives it in `.heximon/nuxt-target.json`, which `nuxi prepare` writes. When the check cannot read the
|
|
196
|
+
preset, it uses the `platform` of `heximon.config.ts`. Without one, it compiles for Node and prints an info,
|
|
197
|
+
`check.host-target-default`, that names the cause and the fix. `heximon check --startup` and
|
|
198
|
+
`heximon task run` also take the sidecar `platform` for such a preset, and stop with an error without one. A
|
|
199
|
+
preset whose platform package does not load fails with `cli.host-strategy-unavailable`, as the build fails.
|
|
190
200
|
- **`heximon skills add` records only what it installed.** A source it could not fetch stays out of
|
|
191
201
|
`heximon.skills`, so `heximon skills sync` never retries a URL that never worked.
|
|
192
202
|
- **A safe durable change is silent until you look for it.** A new queue channel, saga slot, workflow, or
|
|
@@ -220,6 +230,12 @@ the fix instructions plus a non-zero exit code.
|
|
|
220
230
|
committed file, `--startup` fails and says how to write one. The starters do not run `--startup`.
|
|
221
231
|
When an app has no usable route rows, the check prints one line with the first reason, and `--json` carries
|
|
222
232
|
it in `startupNotes`. The `http/route-rows-fallback` warning gives every reason.
|
|
233
|
+
- **`heximon check --startup` records each hostless app.** A Durable Object that `cloudflare.durableObjectGraphs`
|
|
234
|
+
lists boots a hostless app: only the module that lists it and the modules that this module imports.
|
|
235
|
+
`heximon.startup.json` records the modules of each hostless app, and a module that joins one fails the check.
|
|
236
|
+
A module that leaves it, a new hostless app and a removed one are notes. With build output, the check also
|
|
237
|
+
prints the static closure of the chunk that holds the app's boot file, as a note only. `--json` carries both in
|
|
238
|
+
`startupHostlessApps`.
|
|
223
239
|
- **`heximon check --startup` also checks the size of the built server code.** Each production build (`vp build`,
|
|
224
240
|
or a Nitro or Nuxt build) records each server entry that it deploys in `.heximon/server-build.json`: the main
|
|
225
241
|
entry, and the `dist/edge.js` bundle of a Vercel or Netlify build with edge controllers. From each entry, the
|