Ludo | Txtx
Ludo | Txtx
As pointed by @zone117x in another channel, going on the `winget` path might actually be more mainstream, since this package manager will be available by default on every single windows...

Closing, feel free to re-open if that issue still exits in the latest builds.
Thanks for raising this issue. These are exactly the kind of rough edges that we would like to be addressed before considering this lib as a `1.0.0`.
Addressed with https://github.com/hirosystems/clarinet/pull/535
Hi @moodmosaic! In order to help with prioritization, could you help me understand what kind of features / usage could be unblocked with this idea? Thanks!
With the VM being pulled from the stacks-blockchain repo this approach does not seem to be viable anymore, so I'll close this PR.
@obycode can we close this issue?
I understand that the Foundation will be working on this issue, so assigning it to you @MarvinJanssen. Thanks!
Now that we have a solid way architecture for building components via WASM (ie. latest clarity VSCode 1.0), I'll close this issue.