dOrgJelli

Results 89 issues of dOrgJelli

- [x] #1705 - [ ] #1706 - [ ] #1707

type: story

closes: https://github.com/polywrap/toolchain/issues/1335 Upgrade the build manifest to allow for: - custom VM build script - custom VM Dockerfile Additionally I've normalized all naming in the build manifest to be snake-case.

I propose we use `degit` instead of `polywrap create`, as they effectively function the same way. This means we maintain less code, and can use a popular widely-used package: https://www.npmjs.com/package/degit...

type: feature-proposal

**Is your feature request related to a problem? Please describe.** Currently, the wrap wasm & plugin bindings are bundled into the CLI. This means that every time bindings have an...

type: feature-proposal

Currently we have a JS version of this here: https://github.com/polywrap/uniswap/tree/main/v3/sdks/js Blocked by: #1709 Reference: #1704 We should published this to pypi.io as `uniswap-v3-sdk`.

Reference developer experience described here: https://github.com/polywrap/toolchain/issues/1703 Blocked: #1708

Reference developer experience described here: https://github.com/polywrap/toolchain/issues/1703 Blocked: #1705

Currently we have a JS version of this here: https://github.com/polywrap/uniswap/tree/main/v3/sdks/js Blocked by: #1706 Reference: #1704 We should published this to crates.io as `uniswap_v3_sdk`.

Currently we have this here: https://github.com/polywrap/uniswap/tree/main/v3/sdks/js Once issue #1703 is done, we should published this to NPM as `uniswap-v3-sdk`

For Polywrap imports, currently there's no differentiation between dynamic URIs (ex: ENS domains), and static URIs (ex: IPFS CIDs). The usage of dynamic URIs can presents problems, since the underlying...

pri: high
type: feature-proposal