-
Notifications
You must be signed in to change notification settings - Fork 127
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
RangeError: Maximum call stack size exceeded #585
Comments
Hi @bakon11 ! Could you provide code example to reproduce the error ? It would be better if the example will be with package.json file |
Yes of course. I included my package.json and my TX building JS file. The TX just creates a simple pool delegation transaction. Thank you, |
Hmm ok so I was able to get past that error now I am getting:
Here is console output:
THANKS!!! |
My running As for the second one I would agree with this, except I still have the same symptoms as described in the original post except this time it's this error and not the Honestly though, I'm starting to think that maybe I should probably just get WASM loaded properly in my react project like some of the other threads suggest?? Thanks, |
@bakon11 Error with |
No constraints yet, I will start by getting webpack configured properly first and then see about loading up the browser one. Don't want to drag down two issues at once hehe. Thank you. |
Found answer in #586 |
Whenever I use the ASMJS version of the CSL, since version 11.2.x. After I create a single transaction successfully.
The second time around I get the error "RangeError: Maximum call stack size exceeded".
However once I refresh the browser it works again for a single transaction creation?
I am using this with Newest version of React18, Create React App 5 and Webpack5 if this matters.
Again prior to version 11.2.x I did not have this problem, I could create TX's to my heart's content without having to refresh the website.
Please let me know if you need anymore information.
Thanks,
Mike
The text was updated successfully, but these errors were encountered: