create-rsc-kit 0.30.33 → 0.30.34

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/dist/templates.js CHANGED
@@ -802,8 +802,9 @@ A release step or a worker is a file in \`${o.sourceDir}/commands\` with a defau
802
802
  export — \`export default async (args: string[]) => 0\` — run as \`./app migrate\`
803
803
  from the compiled binary or \`node .output/server/commands.mjs migrate\` from a
804
804
  plain build. It shares the app's code, so there is no second entry point or
805
- binary to write. The return value is the exit code, and \`register()\` runs for a
806
- command only if it exports \`register = true\`. A worker's second argument is
805
+ binary to write. The return value is the exit code, and \`instrumentation.ts\` is
806
+ imported, and its \`register()\` run, for a command only if it exports
807
+ \`register = true\`: any other validates the environment it imports itself. A worker's second argument is
807
808
  \`{ signal, deadline }\` (\`CommandContext\`, from \`@rsc-kit/core/commands\`): loop on
808
809
  \`signal.aborted\`, and read \`context.deadline\` when needed, never destructure it.
809
810
  Keep \`--splitting\` in the \`compile\` script: it is what lets a worker hold a stop that arrives while Bun parses the binary. Never run a command as
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "create-rsc-kit",
3
- "version": "0.30.33",
3
+ "version": "0.30.34",
4
4
  "type": "module",
5
5
  "description": "Scaffold an RSC app on Bun, Hono, Elysia or Node.",
6
6
  "bin": {