Replies: 2 comments
-
Why can the SES library not give an error which says which bit of code it had an issue with? The stack just shows that a certain SES library in node_modules had an issue. Can someone improve the error reporting of SES? I had actually had the same problem with axios and then just implemented fetch myself - only to notice that axios is NOT supported in the docs. So now I am having to implement all the Web3 functions my self instead of using the Web3 library and the SES error checking does not even mention that the code it has an issue with is the Web3 dependency - this needs some attention in my opinion. |
Beta Was this translation helpful? Give feedback.
-
Unfortunately SES error reporting is not great. We are working on improving it but in the short term it's going to continue to be painful... I can say with certainty that ethers is compatible with SES. I don't think web3 is. It would have to be patched... |
Beta Was this translation helpful? Give feedback.
-
When I add the following:
"web3": "^4.3.0"
to
packages/snap/package.json
then when I run under packages/snap:
yarn run start
I get the error:
✖ Failed to evaluate snap bundle in SES. This is likely due to an incompatibility with the SES environment in your snap.
Received the following error from the SES environment:
Does this mean that snap does not support the web3 library?
Also the error is not very helpful. How can we know whether a library is supported by SES or not? Also the error does not say which library it has an issue with.
Beta Was this translation helpful? Give feedback.
All reactions