LedgerSigner.connect always throws an error

Describe the bug calling connect on a LedgerSigner instance throws an error

Likely related to the underlying HID transport holding the device, and the new signer making a second acquisition attempt that fails

Reproduction steps

import { LedgerSigner } from '@ethersproject/hardware-wallets'
import * as ethers from 'ethers'

const provider = ethers.providers.getDefaultProvider()
const signer = new LedgerSigner()

signer.connect(provider)

/// Error: cannot open device with path

Environment ts-node w/ node@16.6.2 on an M1 macbook

[mdnorman]

@prestwich thanks! I had issues with the 5.5.0 version as well, and your version seems to work for me. I was thinking of doing something similar after spending a while digging into the @ledgerhq code, so I appreciate it!

Can a contributor get this change added?

[prestwich]

I fixed the issue in Node. This makes ledger Eth objects into singletons, so they are reused by LedgerSigner. This allows instantiation of multiple LedgerSigners, as well as using the Signer.connect() function without error.

I have not yet tested these changes in browser, as that would require updating u2f. Tried to design eth.ts it such that a build system could simply swap out ledger-transport.ts for browser-ledger-transport.ts at build time without issues, and such that we could add more transports easily

Uploading as a zip file, as I can’t find contributor documentation on build/formatting/lint systems. This is intended for packages/hardware-wallets/src.ts

src.ts.zip