@effected/cli 0.9.0 → 0.10.0

package/CliColor.js

@@ -1,5 +1,5 @@
 import { Config, Effect, Layer, Option, Stdio } from "effect";
-import { CliOutput } from "effect/unstable/cli";
+import { CliOutput } from "effect/cli";
 
 //#region src/CliColor.ts
 const noColor = Config.option(Config.String("NO_COLOR"));

package/CliRuntime.js

@@ -4,7 +4,7 @@ import { CliLogger } from "./CliLogger.js";
 import { ExitRequested } from "./internal/ExitRequested.js";
 import { routeHelpOnUsageError } from "./internal/HelpRouting.js";
 import { Cause, Effect, MutableRef, Runtime } from "effect";
-import { CliError } from "effect/unstable/cli";
+import { CliError } from "effect/cli";
 
 //#region src/CliRuntime.ts
 const isShowHelp = (u) => CliError.isCliError(u) && u._tag === "ShowHelp";

package/CliTest.js

@@ -1,5 +1,5 @@
 import { Effect, FileSystem, Path, Stream } from "effect";
-import { ChildProcess, ChildProcessSpawner } from "effect/unstable/process";
+import { ChildProcess, ChildProcessSpawner } from "effect/process";
 
 //#region src/CliTest.ts
 const text = (stream) => Stream.mkString(Stream.decodeText(stream));
@@ -47,7 +47,7 @@ var CliTest = class {
 	* @remarks
 	* `stdin` is never left as an inherited open pipe: when omitted or `""`
 	* the child gets an already-ended empty input (`Stream.empty`), so a
-	* stdin-reading bin exits instead of hanging on `effect/unstable/process`'s
+	* stdin-reading bin exits instead of hanging on `effect/process`'s
 	* default `"pipe"` stdio, which stays open until something writes to and
 	* ends it.
 	*/

package/README.md

@@ -5,7 +5,7 @@
 [![Node.js %3E%3D24.11.0](https://img.shields.io/badge/Node.js-%3E%3D24.11.0-5fa04e.svg)](https://nodejs.org/)
 [![TypeScript 7.0](https://img.shields.io/badge/TypeScript-7.0-3178c6.svg)](https://www.typescriptlang.org/)
 
-The boundary layer of a command-line program built on `effect/unstable/cli`: how output reaches a human, how a failure is reported, and how a schema issue becomes a sentence someone can act on. `CliLogger` renders log records as plain lines and routes diagnostics to stderr, reading the `Console` off the fiber so it needs no platform package and the stream split is actually testable. `CliRuntime.reportFailures` catches inside your program so a failure prints through *your* logger instead of Effect's default one on stdout, then re-fails with the exit code and the no-double-report mark; `CliRuntime.main` assembles a whole program — platform layer, a fresh `CliExit`, failure reporting, and the logger — in the one order that reports every failure well. `CliExit` lets a findings command (a linter that found problems, say) succeed with a non-zero exit code, with finalizers intact on any runtime. `CliColor` decides once, per the no-color.org rule, whether output carries ANSI colour, and hands core's own `CliOutput.Formatter` the same decision. `SchemaIssueRenderer` and `ConfigIssueRenderer` turn issue trees into `unknown key at groups.g.rulesetz`. The `./testing` subpath's `CliTest` spawns a built bin hermetically for a test that wants a real subprocess.
+The boundary layer of a command-line program built on `effect/cli`: how output reaches a human, how a failure is reported, and how a schema issue becomes a sentence someone can act on. `CliLogger` renders log records as plain lines and routes diagnostics to stderr, reading the `Console` off the fiber so it needs no platform package and the stream split is actually testable. `CliRuntime.reportFailures` catches inside your program so a failure prints through *your* logger instead of Effect's default one on stdout, then re-fails with the exit code and the no-double-report mark; `CliRuntime.main` assembles a whole program — platform layer, a fresh `CliExit`, failure reporting, and the logger — in the one order that reports every failure well. `CliExit` lets a findings command (a linter that found problems, say) succeed with a non-zero exit code, with finalizers intact on any runtime. `CliColor` decides once, per the no-color.org rule, whether output carries ANSI colour, and hands core's own `CliOutput.Formatter` the same decision. `SchemaIssueRenderer` and `ConfigIssueRenderer` turn issue trees into `unknown key at groups.g.rulesetz`. The `./testing` subpath's `CliTest` spawns a built bin hermetically for a test that wants a real subprocess.
 
 > **Pre-release.** This package is part of the `@effected/*` kit, in pre-`1.0.0`
 > development against a single pinned Effect v4 prerelease. Packages graduate to
@@ -25,7 +25,7 @@ Everything here shares one property: **you only discover you needed it by shippi
 
 Effect's default logger emits `[00:33:56.619] INFO (#2): message`. That is correct for a service being scraped and wrong for a tool someone is watching — it turns a formatted table into noise — and nothing at the call site suggests it. A platform `runMain` then reports an unhandled failure through that *same* default logger, which sits outside the layers your program was provided, so a program that carefully installs a CLI logger still prints its failures in the format that logger exists to replace, on **stdout**, the one stream errors must not use. And a decode failure arrives as a structured tree when what a user needs is a sentence naming the key they got wrong; core does ship formatters for this, but they live on `SchemaIssue` rather than `SchemaError`, are named `makeFormatter*`, and are not referenced by `SchemaError.message` — two engineers searched for two rounds and concluded they did not exist.
 
-This package is **not a CLI framework**. `effect/unstable/cli` owns argument parsing, flags, the command tree and help, and this package must never grow a second one.
+This package is **not a CLI framework**. `effect/cli` owns argument parsing, flags, the command tree and help, and this package must never grow a second one.
 
 ## Install
 
@@ -104,13 +104,13 @@ Print-then-`reported` is for a program run **without** `CliRuntime.main` or `rep
 
 A findings command — one whose non-zero exit reports a result rather than a
 crash — wires `CliRuntime.main`, `CliExit.set` and `CliColor.formatterLayer`
-around an ordinary `effect/unstable/cli` command:
+around an ordinary `effect/cli` command:
 
 ```ts
 import { CliColor, CliExit, CliRuntime } from "@effected/cli";
 import { NodeRuntime, NodeServices } from "@effect/platform-node";
 import { Console, Effect, Layer } from "effect";
-import { Command, Flag } from "effect/unstable/cli";
+import { Command, Flag } from "effect/cli";
 
 const findProblems = (strict: boolean): ReadonlyArray<string> =>
   strict ? ["missing changeset", "unpinned dependency"] : ["missing changeset"];

package/index.d.ts

@@ -1,5 +1,5 @@
 import { Cause, Context, Effect, Layer, LogLevel, Logger, MutableRef, Stdio } from "effect";
-import { CliOutput } from "effect/unstable/cli";
+import { CliOutput } from "effect/cli";
 import { ConfigValidationError } from "@effected/config-file";
 //#region src/CliColor.d.ts
 /**

package/internal/HelpRouting.js

@@ -1,5 +1,5 @@
 import { Console, Effect } from "effect";
-import { CliOutput } from "effect/unstable/cli";
+import { CliOutput } from "effect/cli";
 
 //#region src/internal/HelpRouting.ts
 const OTHER_METHODS = Object.keys({

package/package.json

@@ -1,8 +1,8 @@
 {
 	"name": "@effected/cli",
-	"version": "0.9.0",
+	"version": "0.10.0",
 	"private": false,
-	"description": "The boundary layer of an effect/unstable/cli program: plain CLI output, failure reporting, and schema-issue rendering",
+	"description": "The boundary layer of an effect/cli program: plain CLI output, failure reporting, and schema-issue rendering",
 	"keywords": [
 		"effect",
 		"cli",
@@ -40,8 +40,8 @@
 		"./package.json": "./package.json"
 	},
 	"peerDependencies": {
-		"@effected/config-file": "^0.12.0",
-		"effect": "4.0.0-rc.117"
+		"@effected/config-file": "^0.13.0",
+		"effect": "4.0.0-rc.118"
 	},
 	"peerDependenciesMeta": {
 		"@effected/config-file": {

package/testing.d.ts

@@ -1,5 +1,5 @@
 import { Effect, FileSystem, Path, PlatformError, Scope } from "effect";
-import { ChildProcessSpawner } from "effect/unstable/process";
+import { ChildProcessSpawner } from "effect/process";
 //#region src/CliTest.d.ts
 /**
  * A hermetic temp directory minted by {@link CliTest.sandbox}, removed when its
@@ -83,7 +83,7 @@ export declare class CliTest {
    * @remarks
    * `stdin` is never left as an inherited open pipe: when omitted or `""`
    * the child gets an already-ended empty input (`Stream.empty`), so a
-   * stdin-reading bin exits instead of hanging on `effect/unstable/process`'s
+   * stdin-reading bin exits instead of hanging on `effect/process`'s
    * default `"pipe"` stdio, which stays open until something writes to and
    * ends it.
    */