fix(lazer-sdk): implemented function to convert all non-string WS frames to an array buffer, then leverage an isomorphic buffer implementation

[benduran]

Partially-resolves PFI-101

Summary

As the title suggests, there was a bug in the lazer Websocket client, which was built and intended to built use isomorphically across browser and server-side JavaScript environments.

However, the current implementation made assumptions that the Buffer class would be available in all environments, when it is not something that exists in the browser.

As such, this PR adds the following:

• Initial conversion of all non-string WebSocket frames to an ArrayBuffer
• Then, pass the created ArrayBuffer into newly-created IsomorphicBuffer.from() function
  This allows all existing logic to remain in place, minimizing changes or needing to create approximations of functions but against the ArrayBuffer class.

Rationale

This feels like the least risky way to fix the issue with isomorphism. This PR does not address the auth token being provided in the QueryString at WSS open time. This will occur in another PR, as that will have some business logic changes that change how connections are created and destroyed.

How has this been tested?

• Current tests cover my changes
• Added new tests
• Manually tested the code

see videos, below

Working in Node

CleanShot.2025-10-15.at.16.12.29.mp4

Working in the browser

CleanShot.2025-10-15.at.16.40.22.mp4

[linear]

PFI-101 Fix browser support in Lazer JS SDK

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
api-reference	Ready	Preview	Comment	Oct 17, 2025 10:57am
component-library	Ready	Preview	Comment	Oct 17, 2025 10:57am
developer-hub	Ready	Preview	Comment	Oct 17, 2025 10:57am
proposals	Ready	Preview	Comment	Oct 17, 2025 10:57am

3 Skipped Deployments

Project	Deployment	Preview	Comments	Updated (UTC)
entropy-explorer	Skipped			Oct 17, 2025 10:57am
insights	Skipped			Oct 17, 2025 10:57am
staking	Skipped			Oct 17, 2025 10:57am

[cprussin]

Overall looks good! I have minor nits / points to consider but nothing that I would block merging on, feel free to consider / address any or disregard as you see fit.

[benduran]

update: given the branch on which this PR was crafted is fairly old, I'm not confident in my knowledge of the changeset context (it's my 4th day, after all 😂 ), I'll be taking some of the feedback given on this PR and crafting the changes on the latest code available on main. I will update this branch and re-tag folks for a final review later today

[benduran]

@cprussin @tejasbadadare would appreciate another pass over this, as I've updated this branch and implement changes with, hopefully, a bit better organization (like the new IsomorphicBuffer.fromWebsocketData() function), to hopefully simplify things.

Responded to most PR feedback left in the prior iteration 🤞

[benduran]

@cprussin @tejasbadadare responded to all PR feedback. I'm going to let this simmer until you all log on for the day, as I haven't released an NPM package here yet and want to be sure I do it in a manner that you all are expecting. I see the Readme has steps outlined, so I'll run with those and ping if I have questions

[benduran]

requires a re-review from you all (thanks for your patience here)

[cprussin]

Excellent!