@stackables/bridge-graphql@1.2.4

Patch Changes

• Updated dependencies [848282b]:
  • @stackables/bridge-core@1.7.0

@stackables/bridge-graphql@1.2.3

Patch Changes

• Updated dependencies [8da19e8]:
  • @stackables/bridge-core@1.6.2

@stackables/bridge-core@1.7.0

Minor Changes

• 848282b Thanks @aarne! - Get syntax highlighting directly in typescript files

  import { bridge, parseBridge } from "@stackables/bridge";
  
  const doc = parseBridge(bridge`
    version 1.5
    bridge Query.hello {
      with input as i
      with output as o
      o.message <- i.name
    }
  `);

@stackables/bridge-core@1.6.2

Patch Changes

• #125 8da19e8 Thanks @aarne! - Bugfixes and stability

  • #123 Unify all Wire types
  • Trace propagation with errors
  • Tool errors enriched with sourcemaps
  • Respect tracing settings for all tools

@stackables/bridge-compiler@2.4.4

Patch Changes

• Updated dependencies [848282b]:
  • @stackables/bridge-core@1.7.0

@stackables/bridge-compiler@2.4.3

Patch Changes

• #125 8da19e8 Thanks @aarne! - Bugfixes and stability

  • #123 Unify all Wire types
  • Trace propagation with errors
  • Tool errors enriched with sourcemaps
  • Respect tracing settings for all tools

• Updated dependencies [8da19e8]:

  • @stackables/bridge-core@1.6.2

@stackables/bridge@2.3.1

Patch Changes

• #118 d6907a2 Thanks @aarne! - Bridge Trace IDs - The engine now returns a compact Trace ID alongside your data (e.g., 0x2a). This ID can be decoded into an exact execution map showing precisely which wires, fallbacks, and conditions activated. Because every bridge has a finite number of execution paths, these IDs are perfect for zero-PII monitoring and bucketing telemetry data.

• Updated dependencies [d6907a2]:

  • @stackables/bridge-core@1.6.1
  • @stackables/bridge-graphql@1.2.2
  • @stackables/bridge-parser@1.4.2

@stackables/bridge-parser@1.4.2

Patch Changes

• Updated dependencies [d6907a2]:
  • @stackables/bridge-core@1.6.1

@stackables/bridge-graphql@1.2.2

Patch Changes

• Updated dependencies [d6907a2]:
  • @stackables/bridge-core@1.6.1

@stackables/bridge-core@1.6.1

Patch Changes

• #118 d6907a2 Thanks @aarne! - Bridge Trace IDs - The engine now returns a compact Trace ID alongside your data (e.g., 0x2a). This ID can be decoded into an exact execution map showing precisely which wires, fallbacks, and conditions activated. Because every bridge has a finite number of execution paths, these IDs are perfect for zero-PII monitoring and bucketing telemetry data.