@bensandee/tooling 0.68.0 → 0.70.0

package/bin/bst.mjs

@@ -0,0 +1,26 @@
+#!/usr/bin/env node
+/**
+ * Stable bin target for `bst`.
+ *
+ * This file exists only so that `node_modules/.bin/bst` can be created, and it is committed
+ * rather than built for exactly that reason. pnpm links bins **during install**, and skips one
+ * whose target is missing -- so pointing `bin` straight at `dist/bin.mjs` works only in a tree
+ * that already happens to be built. A fresh checkout installs before it builds, pnpm warns
+ * (`Failed to create bin ... ENOENT`) and moves on, and building afterwards does not go back and
+ * create the link. Every later `pnpm exec bst` then fails with `Command "bst" not found`, which
+ * is what broke CI on this repo's own `check` script.
+ *
+ * The indirection costs one module load and makes the bin link independent of build state: the
+ * link always exists, and `dist/bin.mjs` only has to be there by the time someone runs it. When
+ * it is not, the failure is an explicit ERR_MODULE_NOT_FOUND naming the missing build output --
+ * a far better error than a command that appears not to exist.
+ *
+ * Consumers installing from the registry get both files (`files` ships `bin` and `dist`) and are
+ * unaffected either way, since a published tarball is always built.
+ *
+ * Loaded with a dynamic `await import` rather than a bare `import "../dist/bin.mjs"`, which is an
+ * unassigned import and trips `import(no-unassigned-import)`. Suppressing that rule would be the
+ * wrong trade for a file whose entire purpose is a side effect: the dynamic form says "run this"
+ * rather than "bring in these bindings", which is what is actually meant here.
+ */
+await import("../dist/bin.mjs");