feat: migrate to npm workspaces #24
Merged
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
ghost
force-pushed
the
migrate-to-npm-workspaces
branch
2 times, most recently
from
4cc8783 to
b8c0cc6
Compare
ghost
force-pushed
the
migrate-to-npm-workspaces
branch
from
b8c0cc6 to
477ae38
Compare
ghost
marked this pull request as ready for review
lcovar
approved these changes
Aug 9, 2024
OttoAllmendinger
added a commit
that referenced
this pull request
Nov 7, 2025
feat(wasm-utxo): add MuSig2 taproot key-path finalization support
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
We already use npm workspaces with api-ts, so we should be able to publish new releases without pushing a new commit to the master branch.