fougere 0.2.0-alpha.2 → 0.4.0-alpha.0

package/README.md

@@ -12,4 +12,4 @@ npx fougere check             # read the model, report what a split would break
 Same binary as [`@fougere/cli`](https://www.npmjs.com/package/@fougere/cli) — this
 package holds no code, only the name. Install either one.
 
-**[Documentation →](https://chok.github.io/fougere/)**
+**[Documentation →](https://fougere.dev/)**

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "fougere",
-  "version": "0.2.0-alpha.2",
+  "version": "0.4.0-alpha.0",
   "description": "The Fougere CLI, under its unscoped name — compose a workspace, serve a frond, call an operation.",
   "keywords": [
     "fougere",
@@ -22,10 +22,11 @@
     "fougere": "dist/bin.js"
   },
   "files": [
-    "dist"
+    "dist",
+    "src"
   ],
   "dependencies": {
-    "@fougere/cli": "0.2.0-alpha.2"
+    "@fougere/cli": "0.4.0-alpha.0"
   },
   "publishConfig": {
     "access": "public"

package/src/bin.ts

@@ -0,0 +1,12 @@
+#!/usr/bin/env node
+/**
+ * `fougere` — the CLI under its unscoped name.
+ *
+ * It holds nothing. `@fougere/cli` already installs a `fougere` binary; this
+ * package exists so that `npx fougere` and `npm i -g fougere` reach it, because
+ * an unscoped name is first-come-first-served and a scope does not reserve it.
+ *
+ * Importing the bin runs it — it is a script, not a module with an entry point,
+ * and `argv` travels untouched.
+ */
+import '@fougere/cli/bin';