🐛 Bug Report: TypeScript Issues in toSigner Function

[joepegler]

Is there an existing issue for this?

• I have searched the existing issues

Package Version

0.1.10

Current Behavior

1. TypeScript shows errors in IDE when passing window.ethereum as a signer to toSigner function
2. signTypedData requires any type casting to work
3. EthereumProvider type definition is incomplete and doesn't properly match window.ethereum's shape
4. Type guards are insufficient for proper type narrowing

Expected Behavior

1. window.ethereum should be accepted as a valid signer type without TypeScript errors
2. signTypedData should work without any type casting
3. EthereumProvider type should accurately reflect the shape of window.ethereum
4. Type guards should properly narrow types for all possible signer variants

Steps To Reproduce

1. Import and use toSigner in a browser environment:
2. Observe TypeScript errors in IDE indicating type incompatibility
3. Check signTypedData implementation:

Package.json (or lockfile) content

No response

Link to Minimal Reproducible Example (StackBlitz, CodeSandbox, GitHub repo etc.)

No response

Anything else?

Related Files

• src/sdk/account/utils/toSigner.ts
• src/sdk/account/types.ts

Impact

• Developers need to use type assertions
• IDE support is compromised
• Type safety is reduced
• Poor developer experience

Workarounds

Currently, developers are forced to:

1. Use type assertions (as any)
2. Ignore TypeScript errors
3. Create intermediate variables with explicit typing