@lunora/errors 1.0.0-alpha.12 → 1.0.0-alpha.14

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. package/dist/index.d.mts +2 -2
  2. package/dist/index.d.ts +2 -2
  3. package/package.json +1 -1
package/dist/index.d.mts CHANGED
@@ -689,12 +689,12 @@ declare const CLOUDFLARE_PLATFORM_ERRORS: ReadonlyArray<CloudflarePlatformError>
689
689
  /**
690
690
  * Recognize a Cloudflare platform-error {@link CloudflarePlatformError} in a raw
691
691
  * error message, conservatively: the message must carry Cloudflare's own
692
- * `Error &lt;code>` phrasing, or mention `cloudflare` alongside the standalone
692
+ * `Error <code>` phrasing, or mention `cloudflare` alongside the standalone
693
693
  * code. That keeps a bare number (`expected 520 items`) from false-matching a 5xx
694
694
  * code, at the cost of missing a context-free code — the safe trade for a
695
695
  * grounded hint. Returns the matched code's {@link Solution}, or `undefined`.
696
696
  *
697
- * Matching runs in two passes, strongest first: Cloudflare's own `Error &lt;code>`
697
+ * Matching runs in two passes, strongest first: Cloudflare's own `Error <code>`
698
698
  * phrasing is unambiguous, so it must win over the weaker "mentions cloudflare
699
699
  * near some number" heuristic regardless of table order. A single pass let a weak
700
700
  * match on an earlier entry beat an explicit match on a later one — `"Cloudflare
package/dist/index.d.ts CHANGED
@@ -689,12 +689,12 @@ declare const CLOUDFLARE_PLATFORM_ERRORS: ReadonlyArray<CloudflarePlatformError>
689
689
  /**
690
690
  * Recognize a Cloudflare platform-error {@link CloudflarePlatformError} in a raw
691
691
  * error message, conservatively: the message must carry Cloudflare's own
692
- * `Error &lt;code>` phrasing, or mention `cloudflare` alongside the standalone
692
+ * `Error <code>` phrasing, or mention `cloudflare` alongside the standalone
693
693
  * code. That keeps a bare number (`expected 520 items`) from false-matching a 5xx
694
694
  * code, at the cost of missing a context-free code — the safe trade for a
695
695
  * grounded hint. Returns the matched code's {@link Solution}, or `undefined`.
696
696
  *
697
- * Matching runs in two passes, strongest first: Cloudflare's own `Error &lt;code>`
697
+ * Matching runs in two passes, strongest first: Cloudflare's own `Error <code>`
698
698
  * phrasing is unambiguous, so it must win over the weaker "mentions cloudflare
699
699
  * near some number" heuristic regardless of table order. A single pass let a weak
700
700
  * match on an earlier entry beat an explicit match on a later one — `"Cloudflare
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@lunora/errors",
3
- "version": "1.0.0-alpha.12",
3
+ "version": "1.0.0-alpha.14",
4
4
  "description": "Unified error layer for Lunora: one LunoraError base + a central catalog of codes, statuses, and actionable hints, rendered across CLI, overlay, Studio, and the client",
5
5
  "keywords": [
6
6
  "cloudflare",