Publish versions of bb.js without WASM stack traces stripped under a new dev tag
#5647
Comments
Savio-Sou
added
A-devops
ludamad
added a commit
that referenced
this issue
Apr 15, 2024
Side step of #5647. This just keeps the debug data for threaded wasm, as the one we expect to use.
AztecBot
pushed a commit
to AztecProtocol/barretenberg
that referenced
this issue
Apr 16, 2024
Side step of AztecProtocol/aztec-packages#5647. This just keeps the debug data for threaded wasm, as the one we expect to use.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem
bb.js is currently published with WASM stack traces stripped before releasing, which makes debugging unreachable errors challenging.
Meanwhile, removing stripping across the board would make the package bulkier in size, possibly 50MB+.
Impact
This initiative currently blocks the further debugging of noir-lang/noir#4409 and noir-lang/noir#4618, which in turn are blocking the development of a number of Noir projects.
Happy Case
Publish bb.js without WASM stack traces stripped under a new
devtag, in parallel to the usual releases with stack traces stripped.Devs debugging problems would use the
devreleases with WASM stack traces, while application production releases use the more optimizedlatestreleases.Alternative Approach
Publish a separate
bb.js-devpackage.The tag approach seems cleaner but both works.
The text was updated successfully, but these errors were encountered: