Bug: Polyfill Problems in XMTP v3

[technohippies]

Describe the bug

Hey team XMTP,

V3 is a huge update, congratulations! I’m having problems with polyfills + workers in v3. I can send/receive about 5-10 messages, and then I routinely get errors from the Worker, which I believe is the stream listener.

I’m getting errors like:

index.js?v=73adc55f:1 Uncaught Error: expected `,` or `}` at line 1 column 20459
    at Worker.s (index.js?v=73adc55f:1:2076)
s @ index.js?v=73adc55f:1
index.js?v=73adc55f:1 Uncaught Error: expected `,` or `}` at line 1 column 21991
    at Worker.s (index.js?v=73adc55f:1:2076)
s @ index.js?v=73adc55f:1
2index.js?v=73adc55f:1 Uncaught Error: expected `,` or `}` at line 1 column 4093
    at Worker.s (index.js?v=73adc55f:1:2076)
s @ index.js?v=73adc55f:1
index.js?v=73adc55f:1 Uncaught Error: expected `,` or `}` at line 1 column 21991
    at Worker.s (index.js?v=73adc55f:1:2076)
s @ index.js?v=73adc55f:1
index.js?v=73adc55f:1 Uncaught Error: expected `,` or `}` at line 1 column 20459
    at Worker.s (index.js?v=73adc55f:1:2076)

I'm not actually looking for a fix, because I've concluded that I need boilerplate in order to understand how to use the browser-sdk. How these polyfills work, both with and without workers doesn't seem trivial.

If you could make a boilerplate with XMTP + Vite v6, it would be much appreciated. My project seems to have it mostly working, but the stream often fails, and messages aren't received from the stream.

Thank you!

Cross listed: https://community.xmtp.org/t/problems-with-stream-v3-workers-polyfills/884

Expected behavior

No response

Steps to reproduce the bug

You can run my project https://github.com/technohippies/scarlett_vite or visit the URL there, but the code is a mess. I had AI try to fix it, and it was mostly successful, but the occasional stream crashes suggest something more.

[technohippies]

I tried cloning xmtp.chat, and it seems to have errors with the workers too? Clearly it's running on the site though, so I must be doing something wrong. Feel free to reach out on Discord if more convenient

[insipx]

Hey @technohippies ! Thanks for the bug report. This should be fixed in an upcoming browser-sdk release, it was fixed in libxmtp in this pr. The root of the issue occurred because of a deserialization bug in the underlying HTTP stream coming from the libxmtp wasm binary.

I'll keep this issue updated with progress on the next release, and close the issue once you are able to confirm it fixed your problem

[technohippies]

Thank you! Regarding the example, didn't realise I had to download the entire project and build from root. Got that working, so I can at least continue building my backend. Looking forward to the release

[rygine]

hey @technohippies, do you still have this issue with the latest browser SDK?

[technohippies]

hey @technohippies, do you still have this issue with the latest browser SDK?

Testing shortly! Thank you!!

[lynhan318]

I'm facing the same problem.

I pushed the code reproduce the issue here:
https://github.com/lynhan318/xmtp-v3-playground