create-solidrt 0.0.65 → 0.0.67

package/README.md

@@ -8,10 +8,10 @@ cd my-app
 bun run dev
 ```
 
-This forwards to `srt init` from `@solidrt/cli`, which writes a starter project
+This forwards to `sol init` from `@solidrt/cli`, which writes a starter project
 (package.json, tsconfig.json, AGENTS.md, src/index.tsx) into a new, empty folder
 and installs the dependencies.
 
-Bun is only used for development: it runs the scaffolder, the `srt` CLI and the
+Bun is only used for development: it runs the scaffolder, the `sol` CLI and the
 dev server. A SolidRT app itself runs on the SolidRT runtime, which embeds its
 own JavaScript engine, so Bun is not needed to run or ship the app.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-solidrt",
-  "version": "0.0.65",
+  "version": "0.0.67",
   "license": "MIT",
   "funding": "https://github.com/sponsors/wellawaretech",
   "author": "Antoine van Wel",

package/src/main.ts

@@ -1,8 +1,8 @@
 // `bun create solidrt <dir>` entry point. A thin wrapper that forwards to
-// `srt init` in @solidrt/cli, so there is one source of truth for what a new
+// `sol init` in @solidrt/cli, so there is one source of truth for what a new
 // SolidRT project looks like. We shell out via `bun x` rather than depend on
 // @solidrt/cli directly, to avoid pulling its native-binary tree into the
-// scaffolder. The empty/existing-folder guard lives in `srt init`.
+// scaffolder. The empty/existing-folder guard lives in `sol init`.
 import pkg from "../package.json" with { type: "json" }
 
 let dir = process.argv[2]
@@ -18,7 +18,7 @@ if (!dir || dir.startsWith("-")) {
 // unpublished 0.0.0 workspace version, which has no npm release to pin to.
 let cli = pkg.version === "0.0.0" ? "@solidrt/cli@latest" : `@solidrt/cli@${pkg.version}`
 
-// Forward any trailing flags to `srt init` untouched.
+// Forward any trailing flags to `sol init` untouched.
 let extra = process.argv.slice(3)
 let proc = Bun.spawnSync(["bun", "x", cli, "init", dir, ...extra], {
   stdin: "inherit",