-
Notifications
You must be signed in to change notification settings - Fork 960
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Used this in angular it seems this error #943
Comments
how to fix it? kindly help me |
we are working on a v6 branch that will have much fewer dependencies and should fix this issue |
v6.0.2 has been released. There may be some changes needed to incorporate the breaking changes. But I believe the reduction in dependencies will eliminate this issue. |
yes @JoshuaSchmidt-OpenSea @ryanio the above screenshot error fixed now after updating to v6.0.2 but now i got this issue |
while compiling in angular project i got the above errors how to resolve it @ryanio |
What version of node are you on? Try minimum Node v16 |
kindly help me out from this issue @ryanio |
Please try with Node v16, to make it easier to change node versions try using nvm https://github.com/nvm-sh/nvm#installing-and-updating |
What if you use the browserified lib/bundle.js? I'm not too familiar with the angular pipeline, you might need to use webpack or some tool in your build process. |
Internal Process
|
can you try Option B in this answer? https://stackoverflow.com/a/71808381 |
yes tried but i can't same issue persist |
I have opened a PR removing PR: #1029 |
@Rubanrubi we have published v6.0.3 on npm with the fix, give us a try and let us know if it helped fixed your issue! |
closing since the dependency you were having trouble with is no longer included. if you are still having issues please open a new issue with details. i would also recommend doing |
@ryanio Thank you so much for your support its working cool ethers v5 and opensea sdk v6.0.3 :) |
I'll be waiting for multi chain support @ryanio Hope it will be launch soon... |
The text was updated successfully, but these errors were encountered: