Closed agazso closed 11 months ago
@agazso, is it the same for @waku/sdk
of 0.0.19
?
@agazso, is it the same for
@waku/sdk
of0.0.19
?
Yes, it is the same with version 0.0.19
I tried out and the first version which starts breaking is 0.0.17
of @waku/sdk
. I see in that version there was a libp2p version upgrade which may explain this.
https://github.com/waku-org/js-waku/releases/tag/sdk-v0.0.17
Origination of the problem is the approach to how vite
works. It's stance is that they do not include anything but browser-related dependencies and if anyone needs they should add polyfills themself.
Tried different ways to handle that on js-waku
level of abstraction but couldn't find any.
So as per advice from Vite - making an issue on the side of libp2p
to address it.
As mitigation following steps can be done:
vite
config;Issue on libp2p
side https://github.com/libp2p/js-libp2p/issues/2110
This is a bug report
Problem
I have an application that uses
@waku/sdk
. I tried upgrading the version of@waku/sdk
from 0.0.16 to 0.0.18 and changed nothing else and now my build is failing (see the error output at the end).It looks like a polyfill issue again coming from libp2p.
Notes
@waku/sdk version 0.0.18 (the latest working that I tried was 0.0.16) Node.js v18.17.1 on Linux
Error output when building: