wrap-cli icon indicating copy to clipboard operation
wrap-cli copied to clipboard

Used to create, build, and integrate wraps.

Results 238 wrap-cli issues
Sort by recently updated
recently updated
newest added

When using the local-dev-ens deploy module, the URI that is output is a mainnet ENS URI, and does not have the `/testnet/` network in the path. I also think it...

type: bug

Optional base types are currently implemented as an Option container in `wasm-as` and `schema/bind`. But to omit optional fields from the function parameters we need a `| null` union type....

I can build a Rust wrapper without issue using `polywrap build`. However, I cannot build with `cargo build` if I have the crate-type value of ["cdylib"] in my cargo.toml. This...

type: bug

The `inspect` CLI command is a proposed command that can be used to fetch build artifacts, given a URI. Proposed UX: ```bash polywrap inspect [options] Fetch a wrapper's build artifacts...

type: feature-proposal

In AssemblyScript wrappers, we can get an interface's registered implementation URIs and use one of the URIs to instantiate an interface module. This makes it possible for us to invoke...

type: bug

Workflow logic should reside in `cli`, and the workflow type should be imported from polywrap-manifest-types-js.

Currently all packages published to the @polywrap npm organization use the same version, defined in [the VERSION file](https://github.com/polywrap/monorepo/blob/prealpha/VERSION). This is not very ideal when we start using proper `MAJOR.MINOR.PATCH` semantic...

type: documentation