Remove sha3, uts46,and graph-node plugins from default client config

[krisbitney]

This PR removes the sha3, uts46, and graph-node plugins from the default client configuration. It redirects the plugin URIs to the sha3, uts46, and graph-node Wasm wrappers that have been added to the integrations repo.

I updated the ENS Wasm wrapper in the integrations repo to Origin 0.3.0 and replaced the embedded ENS wrapper in the test-env-js package with the updated build. A PR is up to merge the ENS wrapper update in the integrations repo: polywrap/wrap-integrations#112

Also related is a PR to add the sha3, uts46, and graph-node plugins to the integrations repo: polywrap/wrap-integrations#110

Closes #1125.

[dOrgJelli]

Can we use an ENS domain here instead? This will ensure it's always kept online by https://wrappers.io

[krisbitney]

Okay, I added the ENS URIs.

export const defaultWrappers = {
  sha3: "wrap://ens/goerli/sha3.wrappers.eth",
  uts46: "wrap://ens/goerli/uts46.wrappers.eth",
  graphNode: "wrap://ens/goerli/graph-node.wrappers.eth",
};

To improve resolution performance, I added a goerli network using the default infura key we use for mainnet in the etherum plugin config:

networks: {
  mainnet: {
    provider:
      "https://mainnet.infura.io/v3/b00b2c2cc09c487685e9fb061256d6a6",
  },
  goerli: {
    provider:
      "https://goerli.infura.io/v3/b00b2c2cc09c487685e9fb061256d6a6",
  },
},

The resolution performance without it isn't very good. That's why I used the IPFS hashes. Let me know what you think! And thanks.

[cbrzn]

I went ahead and added the goerli connection into the Ethereum plugin constructor so we guarantee that the user always has the connection to goerli.

The reason for this is that if a user creates a new instance of the client and passes an Ethereum plugin, it will overwrite the default configuration, removing the goerli connection, hence, not being able to achieve the new wrappers deployed to goerli with ENS Uri resolver

I also think that we should stop setting the configuration in client instantiation (i.e: in test env) and just use the config builder, this way things would be cleaner, but this is another topic 😋

[lgtm-com]

This pull request fixes 3 alerts when merging 6d22bdc into c6d1d0b - view on LGTM.com

fixed alerts:

• 3 for Unused variable, import, function or class