@lifi/perps-sdk-provider-lighter 22.1.0 → 22.1.1

package/README.md

@@ -53,7 +53,11 @@ Each provider instance shares one request hold across its Lighter API clients, p
 
 ## WASM signer loading
 
-The Go signer binary ships as a separate asset and the package resolves it itself. The ESM build points a static `new URL('../../wasm/lighter-signer.wasm', import.meta.url)` at it, which webpack, Turbopack and Vite production builds rewrite into an emitted asset URL, while Node reads the installed binary from disk. The loader checks the WASM preamble of whatever the URL serves; if a bundler relocated the module — Vite's dependency optimizer rewrites the package into `.vite/deps`, leaving the static URL pointing at the cache directory — it re-resolves through that bundler's own asset pipeline. Go's `wasm_exec.js` is packaged as generated text and evaluated as-is.
+The Go signer binary ships as a separate asset that the package resolves itself. The ESM build uses `new URL('../../wasm/lighter-signer.wasm', import.meta.url)`. Webpack, Turbopack, and Vite production builds rewrite this expression into an emitted asset URL. Node reads the installed binary from disk. The loader checks the WASM preamble of the response. Vite's dependency optimizer can relocate the package into `.vite/deps`, which invalidates the static URL. The loader then resolves the asset through the bundler's own asset pipeline.
+
+Go's `wasm_exec.js` ships inside a generated initializer that compiles into both CommonJS and ESM. Package imports do not initialize Go or install its globals. `loadLighterWasm()` initializes the runtime after reading the binary, so callers can install required polyfills after import. The package evaluates no script text.
+
+Under a Content Security Policy, `script-src` must include `'wasm-unsafe-eval'` so the browser can run `WebAssembly.instantiate`. `'unsafe-eval'` is not required.
 
 Applications need no `optimizeDeps.exclude`, no `?url`/`?raw` imports, no `public/` copy step, no caller-supplied URL and no bundler configuration. `loadLighterWasm()` is exported for hosts that want to warm the signer up (and its 12.9 MB download) before the user's first trade:
 
@@ -63,6 +67,21 @@ import { loadLighterWasm } from '@lifi/perps-sdk-provider-lighter'
 await loadLighterWasm()
 ```
 
+## Consumer verification
+
+Run these commands from the repository root:
+
+```sh
+pnpm --filter @lifi/perps-sdk-provider-lighter exec playwright install chromium
+pnpm --filter @lifi/perps-sdk-provider-lighter test:consumers
+```
+
+On Linux systems without browser libraries, use `playwright install --with-deps chromium` for the installation step.
+
+The four Next targets execute the client probe in headless Chromium. They cover development and production with webpack and Turbopack. Browser exceptions, failed probes, missing results, and invalid WASM responses fail the checks. The checks also verify the emitted asset and its chunk reference.
+
+Playwright is a development dependency. SDK consumers do not need it.
+
 ## Documentation
 
 - [`@lifi/perps-sdk` README](https://www.npmjs.com/package/@lifi/perps-sdk) — client setup, options, and the WebSocket API

package/dist/cjs/signers/generated/wasmExecRuntime.d.ts

@@ -1,2 +1,5 @@
-export declare const WASM_EXEC_JS: string;
+export declare function createGoRuntime(): {
+    importObject: WebAssembly.Imports;
+    run(instance: WebAssembly.Instance): Promise<void>;
+};
 //# sourceMappingURL=wasmExecRuntime.d.ts.map

package/dist/cjs/signers/generated/wasmExecRuntime.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"wasmExecRuntime.d.ts","sourceRoot":"","sources":["../../../../src/signers/generated/wasmExecRuntime.ts"],"names":[],"mappings":"AA8jBA,eAAO,MAAM,YAAY,EAAE,MAAmC,CAAA"}
+{"version":3,"file":"wasmExecRuntime.d.ts","sourceRoot":"","sources":["../../../../src/signers/generated/wasmExecRuntime.ts"],"names":[],"mappings":"AAKA,wBAAgB,eAAe,IAAI;IACjC,YAAY,EAAE,WAAW,CAAC,OAAO,CAAA;IACjC,GAAG,CAAC,QAAQ,EAAE,WAAW,CAAC,QAAQ,GAAG,OAAO,CAAC,IAAI,CAAC,CAAA;CACnD,CAojBA"}