@stonyx/logs 1.0.1-alpha.19 → 1.0.1-alpha.20

package/README.md

@@ -232,8 +232,8 @@ your handler, or it prints twice.
 > For the recoverable directory-level codes -- `ENOENT`, `EACCES`, `EPERM`, `EROFS` -- **Log** has
 > already retried internally by the time the rejection reaches you (see
 > [self-healing retry](#self-healing-retry) below), so that retry ran and failed too. Every other
-> code -- `EISDIR`, `ENOTDIR` and `ENOSPC` among them -- is never retried, because a retry cannot
-> help it. Either way a consumer-side retry layer races the internal self-heal or repeats a call that
+> code -- `EISDIR`, `ENOTDIR` and `ENOSPC` among them -- is not itself retried, because a retry
+> cannot help it. Either way a consumer-side retry layer races the internal self-heal or repeats a call that
 > already cannot succeed, and only delays the disable or back-off that your error path exists to
 > trigger.
 >
@@ -307,8 +307,9 @@ re-arm above, which is what makes a recovery notice reachable at all.
 A cached log directory can outlive the directory it describes - for example, something deletes
 `logs/` while your process is running. To cover that, a failure whose `err.code` is `ENOENT`,
 `EACCES`, `EPERM` or `EROFS` drops the cached directory entry and retries the write **exactly once**.
-Any other code -- `EISDIR`, `ENOTDIR`, `ENOSPC`, `EMFILE` and the rest -- rejects on the first
-attempt, with no retry.
+Any other code -- `EISDIR`, `ENOTDIR`, `ENOSPC`, `EMFILE` and the rest -- does not itself trigger
+a retry. The decision is keyed on the *first* attempt's code, so a rejection carrying one of these
+can still arrive after a retry if conditions changed mid-call.
 
 A retry that succeeds emits no *failure* notice: the promise resolves normally and the write counts
 as a success, closing any failure episode already open for that directory with the usual

package/dist/index.d.ts

@@ -106,7 +106,8 @@ export default class Log {
      * stderr notice emitted alongside a failure is informational only and is deduped per episode.
      *
      * On `ENOENT`, `EACCES`, `EPERM` or `EROFS` the cached directory entry is dropped and the write
-     * is retried exactly once; every other code rejects on the first attempt without a retry.
+     * is retried exactly once. Other codes do not themselves trigger a retry; the decision is keyed
+     * on the first attempt's code.
      *
      * A rejection is terminal either way. For those four codes the self-heal has already run and
      * failed by the time one escapes; the rest were never retryable, so repeating the call cannot

package/dist/index.js

@@ -155,7 +155,8 @@ export default class Log {
      * stderr notice emitted alongside a failure is informational only and is deduped per episode.
      *
      * On `ENOENT`, `EACCES`, `EPERM` or `EROFS` the cached directory entry is dropped and the write
-     * is retried exactly once; every other code rejects on the first attempt without a retry.
+     * is retried exactly once. Other codes do not themselves trigger a retry; the decision is keyed
+     * on the first attempt's code.
      *
      * A rejection is terminal either way. For those four codes the self-heal has already run and
      * failed by the time one escapes; the rest were never retryable, so repeating the call cannot

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@stonyx/logs",
-  "version": "1.0.1-alpha.19",
+  "version": "1.0.1-alpha.20",
   "description": "Simplified logging for node applications",
   "type": "module",
   "main": "dist/index.js",