10

Web3.js web3 into the window object.

Browser Wallets like MetaMask inject ethereum into the window object.

In typescript right now to mitigate compile errors I'm casting as follows (window as any).ethereum

After looking in the Web3 repository and Wallet repos (such as MetaMask) there are no importable / copyable typescript definitions / interfaces for the Window object.

A possible solution is to write my own interface and extend the Window, look at the Window object and try to infer the types - not ideal

Other developers that have used web3.js and typescript, how did you get past the Window type interface issues and intellisense suggestions in VS Code?

TylerH
  • 20,799
  • 66
  • 75
  • 101
Xavier
  • 831
  • 3
  • 9
  • 22
  • 1
    Technically, `window.ethereum` is injected by MetaMask or any other in-browser wallet. Note that other wallets **do not** have `window.ethereum`. https://ethereum.stackexchange.com/questions/82531/connecting-the-wallet-of-a-user-to-your-dapp-web3-js-project-and-interacting-w – Mikko Ohtamaa Dec 30 '20 at 09:55
  • Thanks @MikkoOhtamaa i'm assuming that the most popular and adopted wallets are the one's that will inject it into the browser. – Xavier Dec 30 '20 at 09:58
  • You are assuming incorrect. Only browser plugin wallets can inject `ethereum` and most wallets are mobile wallets. – Mikko Ohtamaa Dec 30 '20 at 09:59
  • @MikkoOhtamaa i've updated the question to reflect your explanation, thanks for clarifying. – Xavier Dec 30 '20 at 11:07
  • And your question is still very valid :) But it might be a better ask a generic question "How toa add new `window` variables in TypeScript". Because that is what you want to do, there is nothing Ethereum specific in your question. – Mikko Ohtamaa Dec 30 '20 at 11:11
  • 2
    @MikkoOhtamaa Sorry, but the question I have isn't around extending the interface of the `Window` that is relatively simple to do as documented here: https://stackoverflow.com/questions/12709074/how-do-you-explicitly-set-a-new-property-on-window-in-typescript I'm more interested in how other developers have handled the issue of Web3.js's and MetaMasks's lack of typings for extending the window object. I was digging around the Web3.js repository and found some typings that include the functions available on `window.ethereum` so that might be a good place to start. – Xavier Dec 30 '20 at 14:11

4 Answers4

25

The official Metamask Provider repo now exports types you could/should use for extending the Window interface.

Same as in @Felipe's answer with MetamaskInpageProvider instead of Ethereumish,

import { MetaMaskInpageProvider } from "@metamask/providers";

declare global {
  interface Window {
    ethereum: MetaMaskInpageProvider;
  }
}

Andrew Glago
  • 264
  • 1
  • 4
  • 5
13

I came across this just recently as well. I could not find an appropriate typings package from DefinitelyTyped so I started extrapolating from my own usage and the Metamask Documentation and created something that works so far.

Perhaps the community could edit this answer with their own contributions.

In order to use the ethereum object without TS complaints, I declare it in the window object:

declare global {
    interface Window {
        ethereum: Ethereumish;
    }
}

The makeshift Ethereum Provider types, Ethereumish looks like this:

import { ProviderMessage, ProviderRpcError, ProviderConnectInfo, RequestArguments } from 'hardhat/types';

export interface EthereumEvent {
    connect: ProviderConnectInfo;
    disconnect: ProviderRpcError;
    accountsChanged: Array<string>;
    chainChanged: string;
    message: ProviderMessage
}

type EventKeys = keyof EthereumEvent;
type EventHandler<K extends EventKeys> = (event: EthereumEvent[K]) => void;

export interface Ethereumish {
    autoRefreshOnNetworkChange: boolean;
    chainId: string;
    isMetaMask?: boolean;
    isStatus?: boolean;
    networkVersion: string;
    selectedAddress: any;

    on<K extends EventKeys>(event: K, eventHandler: EventHandler<K>): void;
    enable(): Promise<any>;
    request?: (request: { method: string, params?: Array<any> }) => Promise<any>
    /**
     * @deprecated
     */
    send?: (request: { method: string, params?: Array<any> }, callback: (error: any, response: any) => void) => void
    sendAsync: (request: RequestArguments) => Promise<unknown>
}

As you can see, I have not been able to figure out the exact types of many things so far, but the important methods, send and sendAsync are accurate in my experience.

Another useful template is something I found inside @ethersproject/providers/src.ts/web3-provider.ts

export type ExternalProvider = {
    isMetaMask?: boolean;
    isStatus?: boolean;
    host?: string;
    path?: string;
    sendAsync?: (request: { method: string, params?: Array<any> }, callback: (error: any, response: any) => void) => void
    send?: (request: { method: string, params?: Array<any> }, callback: (error: any, response: any) => void) => void
    request?: (request: { method: string, params?: Array<any> }) => Promise<any>
}

this can be used when loading a new provider

new ethers.providers.Web3Provider(myProvider: ExternalProvider)
Felipe
  • 10,606
  • 5
  • 40
  • 57
  • 3
    This repo from metamask seems to provide the type definition `MetaMaskInpageProvider`: https://github.com/MetaMask/providers – govizlora Jun 20 '21 at 17:26
  • it seems very heavy to import hardhat into client dev just for the type definitions. – dcsan Apr 25 '22 at 21:47
1

I will just dump what I use currently here.

src/{anything}.ts e.g. src/interfaces.d.ts
interface Window {
  // pick one
  ethereum: EthereumProvider
  // ethereum: ExternalProvider
  // ethereum: AbstractProvider
}

// ExternalProvider seems to be the official ethersproject type for the window.ethereum object, however, `new Web3(ethereum)` does not like it so we must improvise.
declare type ExternalProvider = import('@ethersproject/providers').ExternalProvider
declare type AbstractProvider = import('web3/node_modules/web3-core/types').AbstractProvider
interface EthereumProvider extends ExternalProvider {
  _state: {
    accounts: string[]
  }
  on(event: 'close' | 'accountsChanged' | 'chainChanged' | 'networkChanged', callback: (payload: any) => void): void
  once(event: 'close' | 'accountsChanged' | 'chainChanged' | 'networkChanged', callback: (payload: any) => void): void
  removeAllListeners(): void
  sendAsync: AbstractProvider['sendAsync']
}

This file is a script as it does not import and export anything (unlike module), making its declarations ambient - available globally. Just make sure it is included in the tsconfig.json file in the include/blob array "include": ["..."].

More reading:
https://github.com/MetaMask/providers
github.com~ethers.js @ ExternalProvider

Qwerty
  • 29,062
  • 22
  • 108
  • 136
1

My friends, if you are using React with TypeScript just do this and everything goes right! Trust me :)

  1. create global.d.ts in the root of your project and put this code

     declare global {
         interface Window {
             ethereum: import('ethers').providers.ExternalProvider;
         }
     }
     
  2. Then in react-app-env.d.ts put this code

     interface Window {
         ethereum: any;
     }
     

Now you have the code snippet and no error!!