You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
SCHY-148 Use miniflare to test changes in a cloudflare-esque environment to catch issues (#92)
* use miniflare to test builds in a cloudflare environment ( to smoke test cloud flare issues early)
* add replicator/datastream readme
* use webassembly.compile over webassembly.module
* add mroe cloudflare tests cases
* remove console.log
* move cloudflare-compat job to a different workflow to avoid fern regeneration issues
* saving this here for later
* remove cloudflare check from ci for now
* Add cloudflare test script to CI (restoring from removing it in earlier PR)
---------
Co-authored-by: Christopher Brady <chris@schematichq.com>
DataStream enables local flag evaluation by maintaining a WebSocket connection to Schematic and caching flag rules, company, and user data locally.
607
+
608
+
> **Runtime compatibility:** DataStream requires Node.js APIs (`WebSocket`, `EventEmitter`) and is not supported in edge runtimes such as Cloudflare Workers, Vercel Edge Functions, or Deno Deploy. For these runtimes, use [Replicator Mode](#replicator-mode) instead.
Replicator mode is designed for environments where a separate process (the replicator) manages the WebSocket connection and populates a shared cache. The SDK reads from that cache and evaluates flags locally without establishing its own WebSocket connection.
658
+
659
+
### Requirements
660
+
661
+
Replicator mode requires a shared cache (Redis or custom cache providers) so the SDK can read data written by the external replicator process.
0 commit comments