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
It is right now not really possible to profile smoldot in real-world apps because the smoldot Wasm published on NPM has debug info stripped.
Putting the debug info in the Wasm adds around 2MiB to its size, which is unacceptable.
Ideally, the debug info would be in a source map loaded separately. In practice, this is not possible at the moment.
cc #83
We could look at tools that convert DWARF to source maps, but it seems tedious.
Instead, let's ship a second Wasm binary in the smoldot package, and add a new entry point that makes it possible for end users to load that other binary.
The text was updated successfully, but these errors were encountered:
It is right now not really possible to profile smoldot in real-world apps because the smoldot Wasm published on NPM has debug info stripped.
Putting the debug info in the Wasm adds around 2MiB to its size, which is unacceptable.
Ideally, the debug info would be in a source map loaded separately. In practice, this is not possible at the moment.
cc #83
We could look at tools that convert DWARF to source maps, but it seems tedious.
Instead, let's ship a second Wasm binary in the smoldot package, and add a new entry point that makes it possible for end users to load that other binary.
The text was updated successfully, but these errors were encountered: