Fix interaction_ts
import path in package.json (currently hardcoded to local node/
path)
#1535
Labels
Milestone
The current import path for
interaction_ts
in thepackage.json
inbindings/wasm/wasm_identity
is hardcoded to the local node/ path.Instead, we should be pointing to this dependency with a more flexible import, that supports node and web builds.
Unit tests for node WASM builds were running into issue due to being unable to find the
@iota/iota-interaction-ts/move_calls/identity
dependency as well, which sounds like it's related to this issue, e.g.:The text was updated successfully, but these errors were encountered: