Closed phungleson closed 1 year ago
I'm getting this exact error as well with the update. The stack trace is massive, and looks like a lot of entries are from Felte: https://felte.dev/docs/solid/getting-started
I'm running into the same thing. In my case, I am getting this when I have a component wrapped in <Suspense>. If I remove the Suspense wrapper, then the error goes away. Trying to dig in to see if I can figure out what is going on, but wanted to post in case this helps anyone troubleshoot.
Anyone got a quick reproduction? I did change context internals, but it passed local tests, and a streaming hydrating SSR demo I have in the repo. Probably just missed something easy to fix so really helpful if I can get an example. fn not being a function suggests something higher up is not quite right..
EDIT: Actually I think I know what it is.. SuspenseContext has a default value and the old lookup didn't return it so it is improperly thinking nodes are in Suspense. Then later when it tries to run it checks if they are inFallback expecting to run a function and it is just an undefined property on an empty object.
Describe the bug
When I updated to 1.7.10 and ran some tests and I got this error.
I checked my code and all
untrack
is calling with() => {}
.I reverted back to
1.7.9
and tests passed again.Maybe there are issues with other libraries (i.e. testing library), let me know if you need more information, happy to look into this, thanks!
Your Example Website or App
N/A
Steps to Reproduce the Bug or Issue
N/A
Expected behavior
N/A
Screenshots or Videos
No response
Platform
Additional context
No response