create-solidrt 0.0.13

package/README.md

@@ -0,0 +1,13 @@
+# create-solidrt
+
+Scaffold a new [SolidRT](https://github.com/antoinevanwel/solidrt) project:
+
+```sh
+bun create solidrt my-app
+cd my-app
+bunx srt run src/index.tsx
+```
+
+This forwards to `srt 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.

package/bin/create-solidrt

@@ -0,0 +1,2 @@
+#!/usr/bin/env bun
+import "../src/main"

package/package.json

@@ -0,0 +1,15 @@
+{
+  "name": "create-solidrt",
+  "version": "0.0.13",
+  "license": "MIT",
+  "author": "Antoine van Wel",
+  "type": "module",
+  "bin": {
+    "create-solidrt": "./bin/create-solidrt"
+  },
+  "files": [
+    "bin/",
+    "src/",
+    "README.md"
+  ]
+}

package/src/main.ts

@@ -0,0 +1,18 @@
+// `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
+// 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`.
+
+let dir = process.argv[2]
+if (!dir || dir.startsWith("-")) {
+  console.error("Usage: bun create solidrt <dir>")
+  process.exit(1)
+}
+
+let proc = Bun.spawnSync(["bun", "x", "@solidrt/cli", "init", dir], {
+  stdin: "inherit",
+  stdout: "inherit",
+  stderr: "inherit",
+})
+process.exit(proc.exitCode ?? 0)