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
Today aztec.js depends on both types and circuits.js, and types also depends on circuits.js. It can happen that npm or yarn decides to install a copy of circuits.js within aztec.js and another within types, in case there's already a circuits.js in the root of node_modules with a different version. This has led to serialisation issues (see #1826), and can lead to multiple copies of the circuits wasm being loaded, which can have an impact on memory usage.
We should explore whether removing the dependency from aztec.js to circuits.js (and instead having types re-export everything that's needed) would solve the issue. This also requires analysing all other dependencies to circuits.js.
The text was updated successfully, but these errors were encountered:
Today
aztec.js
depends on bothtypes
andcircuits.js
, andtypes
also depends oncircuits.js
. It can happen that npm or yarn decides to install a copy ofcircuits.js
withinaztec.js
and another withintypes
, in case there's already acircuits.js
in the root ofnode_modules
with a different version. This has led to serialisation issues (see #1826), and can lead to multiple copies of the circuits wasm being loaded, which can have an impact on memory usage.We should explore whether removing the dependency from
aztec.js
tocircuits.js
(and instead havingtypes
re-export everything that's needed) would solve the issue. This also requires analysing all other dependencies tocircuits.js
.The text was updated successfully, but these errors were encountered: