@shipeasy/sdk - npm Package Compare versions

Comparing version 9.0.0 to 9.0.1

dist/client/index.d.mts

@@ -93,7 +93,9 @@ /** Project capabilities the devtools overlays render against. This is the
      *
-     * Extras may be folded into the terminal inline as `.to(outcome, extras)` —
-     * equivalent to a final `.extras(...)` (merged over any earlier `.extras`,
-     * later wins), so there is no ordering to remember. A stray `.extras` chained
-     * AFTER `.to` is still harmless: it merges too but only if the microtask
-     * hasn't flushed yet (same as before).
+     * Extras go AFTER the terminal — `.to(outcome).extras({...})` — so the
+     * consequence sentence stays whole; the chain dispatches on the next
+     * microtask, so the trailing extras still make the report. They may also be
+     * folded inline as `.to(outcome, extras)`, equivalent to a final
+     * `.extras(...)` (merged over any earlier `.extras`, later wins). Never wedge
+     * `.extras()` between `.causes_the` and `.to`: it splits the sentence in half
+     * and is hard to read.
      */
@@ -100,0 +102,0 @@ to(outcome: string, extras?: SeeExtras): SeeExtrasTail;

dist/client/index.d.ts

@@ -93,7 +93,9 @@ /** Project capabilities the devtools overlays render against. This is the
      *
-     * Extras may be folded into the terminal inline as `.to(outcome, extras)` —
-     * equivalent to a final `.extras(...)` (merged over any earlier `.extras`,
-     * later wins), so there is no ordering to remember. A stray `.extras` chained
-     * AFTER `.to` is still harmless: it merges too but only if the microtask
-     * hasn't flushed yet (same as before).
+     * Extras go AFTER the terminal — `.to(outcome).extras({...})` — so the
+     * consequence sentence stays whole; the chain dispatches on the next
+     * microtask, so the trailing extras still make the report. They may also be
+     * folded inline as `.to(outcome, extras)`, equivalent to a final
+     * `.extras(...)` (merged over any earlier `.extras`, later wins). Never wedge
+     * `.extras()` between `.causes_the` and `.to`: it splits the sentence in half
+     * and is hard to read.
      */
@@ -100,0 +102,0 @@ to(outcome: string, extras?: SeeExtras): SeeExtrasTail;

dist/devtools-contract/index.d.mts

@@ -215,7 +215,9 @@ /** Project capabilities the devtools overlays render against. This is the
      *
-     * Extras may be folded into the terminal inline as `.to(outcome, extras)` —
-     * equivalent to a final `.extras(...)` (merged over any earlier `.extras`,
-     * later wins), so there is no ordering to remember. A stray `.extras` chained
-     * AFTER `.to` is still harmless: it merges too but only if the microtask
-     * hasn't flushed yet (same as before).
+     * Extras go AFTER the terminal — `.to(outcome).extras({...})` — so the
+     * consequence sentence stays whole; the chain dispatches on the next
+     * microtask, so the trailing extras still make the report. They may also be
+     * folded inline as `.to(outcome, extras)`, equivalent to a final
+     * `.extras(...)` (merged over any earlier `.extras`, later wins). Never wedge
+     * `.extras()` between `.causes_the` and `.to`: it splits the sentence in half
+     * and is hard to read.
      */
@@ -222,0 +224,0 @@ to(outcome: string, extras?: SeeExtras): SeeExtrasTail;

dist/devtools-contract/index.d.ts

@@ -215,7 +215,9 @@ /** Project capabilities the devtools overlays render against. This is the
      *
-     * Extras may be folded into the terminal inline as `.to(outcome, extras)` —
-     * equivalent to a final `.extras(...)` (merged over any earlier `.extras`,
-     * later wins), so there is no ordering to remember. A stray `.extras` chained
-     * AFTER `.to` is still harmless: it merges too but only if the microtask
-     * hasn't flushed yet (same as before).
+     * Extras go AFTER the terminal — `.to(outcome).extras({...})` — so the
+     * consequence sentence stays whole; the chain dispatches on the next
+     * microtask, so the trailing extras still make the report. They may also be
+     * folded inline as `.to(outcome, extras)`, equivalent to a final
+     * `.extras(...)` (merged over any earlier `.extras`, later wins). Never wedge
+     * `.extras()` between `.causes_the` and `.to`: it splits the sentence in half
+     * and is hard to read.
      */
@@ -222,0 +224,0 @@ to(outcome: string, extras?: SeeExtras): SeeExtrasTail;

dist/server/index.d.mts

@@ -93,7 +93,9 @@ import { AsyncLocalStorage } from 'node:async_hooks';
      *
-     * Extras may be folded into the terminal inline as `.to(outcome, extras)` —
-     * equivalent to a final `.extras(...)` (merged over any earlier `.extras`,
-     * later wins), so there is no ordering to remember. A stray `.extras` chained
-     * AFTER `.to` is still harmless: it merges too but only if the microtask
-     * hasn't flushed yet (same as before).
+     * Extras go AFTER the terminal — `.to(outcome).extras({...})` — so the
+     * consequence sentence stays whole; the chain dispatches on the next
+     * microtask, so the trailing extras still make the report. They may also be
+     * folded inline as `.to(outcome, extras)`, equivalent to a final
+     * `.extras(...)` (merged over any earlier `.extras`, later wins). Never wedge
+     * `.extras()` between `.causes_the` and `.to`: it splits the sentence in half
+     * and is hard to read.
      */
@@ -100,0 +102,0 @@ to(outcome: string, extras?: SeeExtras): SeeExtrasTail;

dist/server/index.d.ts

@@ -93,7 +93,9 @@ import { AsyncLocalStorage } from 'node:async_hooks';
      *
-     * Extras may be folded into the terminal inline as `.to(outcome, extras)` —
-     * equivalent to a final `.extras(...)` (merged over any earlier `.extras`,
-     * later wins), so there is no ordering to remember. A stray `.extras` chained
-     * AFTER `.to` is still harmless: it merges too but only if the microtask
-     * hasn't flushed yet (same as before).
+     * Extras go AFTER the terminal — `.to(outcome).extras({...})` — so the
+     * consequence sentence stays whole; the chain dispatches on the next
+     * microtask, so the trailing extras still make the report. They may also be
+     * folded inline as `.to(outcome, extras)`, equivalent to a final
+     * `.extras(...)` (merged over any earlier `.extras`, later wins). Never wedge
+     * `.extras()` between `.causes_the` and `.to`: it splits the sentence in half
+     * and is hard to read.
      */
@@ -100,0 +102,0 @@ to(outcome: string, extras?: SeeExtras): SeeExtrasTail;

docs/skill/SKILL.md

@@ -105,4 +105,6 @@ ---
 try { await submitOrder(order); }
-catch (e) { see(e).causes_the("checkout").to("use cached prices", { order_id: order.id }); }
-// extras inline on .to (no ordering to remember), or chained: .extras({...}).to(...)
+catch (e) { see(e).causes_the("checkout").to("use cached prices").extras({ order_id: order.id }); }
+// Extras go AFTER the terminal (TS defers dispatch a microtask) or inline on it
+// as .to(outcome, obj). NEVER .causes_the(x).extras({...}).to(y) — it splits the
+// consequence sentence in half.
 
@@ -109,0 +111,0 @@ see.Violation("large query").causes_the("results").to("be trimmed").extras({ rows });

package.json

 {
   "name": "@shipeasy/sdk",
-  "version": "9.0.0",
-  "description": "Shipeasy SDK \u2014 feature gates, runtime configs, experiments, and metrics for the Shipeasy hosted service.",
+  "version": "9.0.1",
+  "description": "Shipeasy SDK — feature gates, runtime configs, experiments, and metrics for the Shipeasy hosted service.",
   "license": "SEE LICENSE IN LICENSE",
@@ -6,0 +6,0 @@ "homepage": "https://shipeasy.ai",

New alerts

URL strings

Supply chain risk

Package contains fragments of external URLs or IP addresses, which the package may be accessing at runtime.

Fixed alerts

Major refactor

Supply chain risk

Package has recently undergone a major refactor. It may be unstable or indicate significant internal changes. Use caution when updating to versions that include significant changes.

URL strings

Supply chain risk

Package contains fragments of external URLs or IP addresses, which the package may be accessing at runtime.

Improved metrics

Total package byte prevSize

634705

0.14%

Lines of code

13126

0.05%

Number of medium supply chain risk alerts

30

-3.23%

No dependency changes