@effected/cli 0.4.1 → 0.5.0

package/CliRuntime.js

@@ -87,21 +87,13 @@ var CliRuntime = class CliRuntime {
 			return yield* Effect.fail(CliRuntime.reported(error, chooseExitCode(error, options.exitCode)));
 		});
 	}));
-	/**
-	* Mark an error as already reported, carrying an exit code.
-	*
-	* @remarks
-	* Exported because a program that reports a failure itself — a validation
-	* command that prints its own diagnostics, say — needs the same two marks
-	* and should not have to rediscover the inverted polarity.
-	*/
-	static reported = (error, exitCode = 1) => {
+	static reported(error, exitCode = 1) {
 		const marked = error instanceof Error ? error : new Error(String(error));
 		return Object.assign(marked, {
 			[Runtime.errorReported]: false,
 			[Runtime.errorExitCode]: exitCode
 		});
-	};
+	}
 };
 
 //#endregion

package/README.md

@@ -101,7 +101,7 @@ ConfigValidationError: Config validation failed at "/home/me/.config/app/config.
 - `CliLogger.layer(options?)` — replaces the default logger with plain lines, routing `Error` and above to stderr. The threshold is the `stderrFrom` option, compared ordinally, so a level added upstream lands on the right stream without a change here.
 - `CliLogger.make(options?)` — the `Logger` itself, for composing into a logger set you already have.
 - `CliRuntime.reportFailures(options?)` — reports through your logger, then re-fails with an exit code and the mark that stops the runtime reporting it a second time.
-- `CliRuntime.reported(error, exitCode?)` — marks an error you reported yourself, so the runtime stays quiet about it.
+- `CliRuntime.reported(error, exitCode?)` — marks an error you reported yourself, so the runtime stays quiet about it. A typed `Error` comes back as its own type (the marks are added in place) when it passes `instanceof Error` at runtime; any other value — including one that only satisfies `Error`'s shape structurally — is wrapped in a plain `Error`.
 - `SchemaIssueRenderer.render(issue)` — a `SchemaIssue` tree becomes one line per rejected value.
 - `ConfigIssueRenderer.render(error)` — the same rendering, reading `issue` off a `ConfigValidationError`.
 

package/index.d.ts

@@ -189,8 +189,22 @@ export declare class CliRuntime {
    * Exported because a program that reports a failure itself — a validation
    * command that prints its own diagnostics, say — needs the same two marks
    * and should not have to rediscover the inverted polarity.
+   *
+   * The marks are added in place, so a typed error comes back as its own
+   * type: the `E` overload returns the very instance it was given, and a
+   * program failing with it keeps `catchTags` narrowing downstream without a
+   * cast. Any other value takes the `unknown` fallback and is wrapped in a
+   * plain `Error`.
+   *
+   * The `E extends Error` constraint is structural, not nominal — TypeScript
+   * cannot express "is really an `Error`", so the guarantee holds only when
+   * the argument passes `instanceof Error` at runtime. A value that merely
+   * satisfies `Error`'s shape (an object `implements Error`, or an error
+   * revived from JSON) still takes the wrapping branch and comes back as a
+   * fresh, stripped `Error` typed as `E`.
    */
-  static readonly reported: (error: unknown, exitCode?: number) => Error;
+  static reported<E extends Error>(error: E, exitCode?: number): E;
+  static reported(error: unknown, exitCode?: number): Error;
 }
 //#endregion
 //#region src/ConfigIssueRenderer.d.ts

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@effected/cli",
-	"version": "0.4.1",
+	"version": "0.5.0",
 	"private": false,
 	"description": "The boundary layer of an effect/unstable/cli program: plain CLI output, failure reporting, and schema-issue rendering",
 	"keywords": [