@fusion.dev/create-helix-app 0.0.0-dev

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Fusion Development Group
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -0,0 +1,33 @@
+# @fusion.dev/create-helix-app
+
+Starts a Helix project.
+
+```sh
+npm create @fusion.dev/helix-app@latest my-app
+```
+
+Named without a template, it lists the templates and writes nothing: a
+scaffolder that picks for you writes a project you didn't choose. Name one after
+`--`, which is how `npm create` passes a flag on rather than reading it itself:
+
+```sh
+npm create @fusion.dev/helix-app@latest my-app -- --template react-vite
+```
+
+| Template | What it is |
+|---|---|
+| `react-vite` | React and TypeScript on Vite. The shortest path to a running component. |
+| `react-nextjs` | React and TypeScript on the Next.js App Router, elements registered once. |
+
+This is `helix new` from
+[`@fusion.dev/helix-cli`](https://www.npmjs.com/package/@fusion.dev/helix-cli),
+reached from somewhere with no project yet. A project that already has Helix
+installed can run `npx helix new` instead, and gets the same templates.
+
+**Scoped because the plain name is taken.** `create-helix-app` on npm belongs to
+an unrelated project, so `npm create helix-app` runs somebody else's code.
+`npm create @fusion.dev/helix-app` resolves to this package and no other.
+
+[Documentation](https://helix.fusion.dev)
+
+MIT

package/bin.mjs

@@ -0,0 +1,37 @@
+#!/usr/bin/env node
+/**
+ * `npm create @fusion.dev/helix-app`: `helix new` for somebody with no project
+ * yet.
+ *
+ * **One implementation, two doors.** The scaffolding belongs to the binary, and
+ * this is the door for a reader with nothing installed: npm fetches this
+ * package, the command it depends on, the binary for their machine and the
+ * templates, and this runs `helix new` against the templates it came with.
+ * Nothing here copies or substitutes, which is the part that would drift from
+ * the other door.
+ *
+ * **It names the templates rather than letting the binary look.** `helix new`
+ * walks up from where it is run for a `node_modules` holding them, and the
+ * directory a reader runs this in has none: npm installed everything into its
+ * own cache. So this hands over the package it resolved, which is the one
+ * versioned with the binary beside it. `HELIX_TEMPLATES` already set wins, as it
+ * does everywhere else it is read.
+ */
+import { spawnSync } from 'node:child_process'
+import { createRequire } from 'node:module'
+import { dirname } from 'node:path'
+
+const require = createRequire(import.meta.url)
+const templates = dirname(require.resolve('@fusion.dev/helix-templates/templates.json'))
+const helix = require.resolve('@fusion.dev/helix-cli/bin.mjs')
+
+const { status, error } = spawnSync(process.execPath, [helix, 'new', ...process.argv.slice(2)], {
+  env: { ...process.env, HELIX_TEMPLATES: process.env.HELIX_TEMPLATES ?? templates },
+  stdio: 'inherit',
+})
+/* A status means it ran, whatever `error` says: see the same line in the shim. */
+if (error && status === null) {
+  console.error(`create-helix-app: could not run helix: ${error.message}`)
+  process.exit(70)
+}
+process.exit(status ?? 70)

package/package.json

@@ -0,0 +1,38 @@
+{
+  "name": "@fusion.dev/create-helix-app",
+  "description": "Starts a Helix project: `npm create @fusion.dev/helix-app`, which is `helix new` for somebody with no project yet.",
+  "version": "0.0.0-dev",
+  "license": "MIT",
+  "author": "Ross Sheppard <ross.sheppard@fusion.dev>",
+  "repository": {
+    "directory": "helix/create-app",
+    "type": "git",
+    "url": "git+https://github.com/project-fusion/fusion.git"
+  },
+  "type": "module",
+  "files": [
+    "bin.mjs"
+  ],
+  "bin": {
+    "create-helix-app": "./bin.mjs"
+  },
+  "scripts": {
+    "test": "bun test"
+  },
+  "bugs": "https://github.com/project-fusion/fusion/issues",
+  "dependencies": {
+    "@fusion.dev/helix-cli": "0.24.1",
+    "@fusion.dev/helix-templates": "0.24.1"
+  },
+  "homepage": "https://fusion.dev",
+  "keywords": [
+    "helix",
+    "create",
+    "scaffold",
+    "template",
+    "design-system"
+  ],
+  "publishConfig": {
+    "access": "restricted"
+  }
+}