-
Notifications
You must be signed in to change notification settings - Fork 17
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
TypeError: Cannot read property 'requestRegen' of null #98
Comments
Mmm, it seems a similar errors occurs when reverting the SodiumJS 1.1.3 (send being called before listeners are attached, and that gets rethrown), so this problem must have been introduced by upgrading other packages. With the latest version (3.0.5) this |
I wonder if sodium-frp-react library has bundled its own sodiumjs with its own global scope separate from the global scope of sodium-frp-react-demo. Sort of like the library is loaded twice and it is passing sodium objects between the two sodium libraries. In other words one sodium lib currentTransaction is not null, and the other bundled sodium lib currentTransaction is null. Like #50. |
Might have to try:
On both and include sodium initially in a script tag. Bit messy though. |
Similar issue here with angular. This guy has a solution. (Make sodiumjs a "peerDependency" in sodium-frp-react) |
Ah! Thanks a lot, I will try that |
I'm trying to port my old
sodium-frp-react-demo
to the latest versions of SodiumJS and ReactJS, but I get a crash when running, any idea what this might be? I'm creating cell loops, so I do this insideTransaction.Run
, but this crashes in the latest version, works fine in the very old version I was using.Stack trace:
The text was updated successfully, but these errors were encountered: