For information on how to create your own Polywrap plugin, read the guide here.
Plugins can be used to enable any native client functionality that cannot be implemented in WebAssembly, such as sending HTTP requests, or signing blockchain transactions with a private key.
The Polywrap client has a default configuration that enables developers to use the following plugins:
NOTE: This default configuration will be removed in the near future, and replaced by a "config builder". This will make the client agnostic, and allow users to combine and customize different "config bundles", in addition to creating their your own.
Plugin wrappers are configured using URI Redirects. We would specify the
uri property as the URI of the plugin we want to use, and the
plugin property as the actual plugin.
For example, we can add an Ethereum plugin that uses MetaMask (or any other Ethereum JS provider) for its provider & signer!