wrap-cli
wrap-cli copied to clipboard
polywrap
Used to create, build, and integrate wraps.
**Is your feature request related to a problem? Please describe.** Currently we do not have a clean way of testing multiple wasm languages, and forming a feature matrix. We now...
# Motivation Currently the `polywrap build` command requires docker, which has a few down-sides: - new developer startup cost is high, as base images need to be downloaded - slow...
Currently we just have simple sanity test in schema-bind which may miss a lot of things, we should have fine-grained tests for all the code binding to better cover this...
Blocked by: https://github.com/polywrap/toolchain/issues/1259
I noticed while using deploy manifest that it's not setting the resolver address for the subdomains. Manifest: ```yaml format: "0.2.0" jobs: test: config: provider: $IPFS_GATEWAY_URI gatewayUri: $IPFS_GATEWAY_URI ensRegistryAddress: $ENS_REG_ADDR ensRegistrarAddress:...
Plugin types and all mention of plugins should be removed from client-js and core-js packages. After they URI resolution refactor and the addition of PackageResolver they can now be treated...
Requires: https://github.com/Web3-API/monorepo/issues/201 Create tooling to support various common continuous deployment use-cases. For example, GitHub Actions.
**Is your feature request related to a problem? Please describe.** The JS client should support WASI. **Describe the solution you'd like** We can use the `@wasmer/wasi` package, that works in...