feat: remove exports field to enable deep imports #60
+0
−31
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The exports field was preventing consumers from importing internal WASM wrapper files like 'dist/browser/js/wasm/wasm_utxo.js', which caused build failures in bitgo-ui during the migration from wasm-miniscript to wasm-utxo. The wasm-miniscript package did not have an exports field, allowing all files to be accessible. Removing the exports field from wasm-utxo restores this behavior and allows bitgo-ui to use the existing webpack configuration without modifications. This change enables: - Direct imports of WASM initialization wrapper files - Compatibility with existing build tooling that expects deep imports - Drop-in replacement for wasm-miniscript without code changes Resolves module resolution errors when building bitgo-ui with wasm-utxo. Ticket: BTC-0
bitgoAaron
approved these changes
Nov 13, 2025
davidkaplanbitgo
approved these changes
Nov 13, 2025
Contributor
can we add the required exports field so that it bitgo-ui can access this? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The exports field was preventing consumers from importing internal WASM wrapper files like 'dist/browser/js/wasm/wasm_utxo.js', which caused build failures in bitgo-ui during the migration from wasm-miniscript to wasm-utxo.
The wasm-miniscript package did not have an exports field, allowing all files to be accessible. Removing the exports field from wasm-utxo restores this behavior and allows bitgo-ui to use the existing webpack configuration without modifications.
This change enables:
Resolves module resolution errors when building bitgo-ui with wasm-utxo.
Ticket: BTC-0