@grosspoetrysystems/oompf 0.1.0 → 0.1.1

package/README.md

@@ -29,18 +29,26 @@ and serves **metadata only**.
 
 ## Install
 
+`oompf` is a terminal command, so install it globally:
+
 ```bash
-bunx @grosspoetrysystems/oompf@latest --help
+npm install -g @grosspoetrysystems/oompf
 ```
 
-Or keep it on `PATH`:
+Or run it without installing:
 
 ```bash
-npm install -g @grosspoetrysystems/oompf
+bunx @grosspoetrysystems/oompf@latest --help
+npx @grosspoetrysystems/oompf@latest --help
 ```
 
-The package is scoped; the binary is plain `oompf`. Examples below use the
-binary name.
+The package name is scoped; the command is plain `oompf`, which is what the
+examples below use.
+
+A project-local `npm install` is the wrong shape here: the binary lands in
+`node_modules/.bin`, which is not on your `PATH`, and npm refuses the install
+entirely inside a repository that uses `workspace:` specifiers. Use `-g` or
+`bunx`.
 
 Working in a clone of the repository? Run it from source with
 `bun apps/cli/src/index.ts <command>`.

package/dist/index.d.mts

@@ -171,7 +171,7 @@ interface CliDeps {
  * Must match `package.json`; `index.test.ts` asserts it, because a published
  * binary reporting the wrong version makes every bug report ambiguous.
  */
-declare const CLI_VERSION = "0.1.0";
+declare const CLI_VERSION = "0.1.1";
 /** Build the OOMPF CLI with the given (optional) injectable seams. */
 declare function createCli(deps?: CliDeps): Cli.Cli<{}, undefined, undefined, undefined>;
 //#endregion

package/dist/index.mjs

@@ -8441,7 +8441,7 @@ function registerSearch(cli, deps) {
 * Must match `package.json`; `index.test.ts` asserts it, because a published
 * binary reporting the wrong version makes every bug report ambiguous.
 */
-const CLI_VERSION = "0.1.0";
+const CLI_VERSION = "0.1.1";
 /** Build the OOMPF CLI with the given (optional) injectable seams. */
 function createCli(deps = {}) {
 	const resolved = resolveDeps(deps);