-
-
Notifications
You must be signed in to change notification settings - Fork 95
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
Bug - v1.3.x Throws Errors when Used in React #350
Comments
I'm also getting errors. I got the above and also TypeError: Cannot read properties of undefined (reading 'next') |
Please add reproduction |
@XantreGodlike to preproduce:
npx create-remix@latest
npm add @preact/signals-react
|
I'm working on fixes for this. More coming soon |
btw there are issues with react-native #346 i will try to add good repro too. I think this issues can be related |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Overview
Began using v1.2.2 ~3 weeks ago and it worked whether using new Signal() or signal outside of react component, or when using useSignal() within a component. Started a new project and automatically picked up v1.3.1. As soon as I began implementing signals, the app immediately broke.
Packages (using remix.run + React)
Remix.run - 1.1.15
Node.js - v18.12.0
The error thrown is:
There are also some other things related to goroutines and esbuild errors that throw:
Temporary Solution
Rollback to v1.2.2.
The text was updated successfully, but these errors were encountered: