Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
_TypedDataEncoder was not found in @ethersproject/hash
See original GitHub issueI recently upgraded to webpack 5 and am now seeing this warning in the browser console:
{
"moduleName": "./node_modules/@ethersproject/providers/lib.esm/json-rpc-provider.js",
"loc": "194:36-66",
"message": "export '_TypedDataEncoder' (imported as '_TypedDataEncoder') was not found in '@ethersproject/hash' (possible exports: hashMessage, id, isValidName, messagePrefix, namehash)"
}
Doesn’t seem to affect anything but thought I’d bring it up regardless
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:6 (2 by maintainers)
Top Results From Across the Web
TypeError when using _TypedDataEncoder hash function for ...
Describe the bug Trying to get the EIP712 structHash with ethers to call a contract function and disallow a previously approved offchain ...
Read more >Hashing Algorithms - Hethers - Hedera
Creates a new TypedDataEncoder for types. This object is a fairly low-level object that most developers should not require using instances directly.
Read more >Hashing Algorithms - ethers
Creates a new TypedDataEncoder for types. This object is a fairly low-level object that most developers should not require using instances directly.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Yes that fixed it, deleting the lock file. thanks.
Removing all node_modules directories and deleting yarn.lock seems to have fixed it. Thanks