Closed natew closed 9 years ago
Ah, I'm on 0.13 that may be it.
I haven't tried it with 0.13 yet, will do soon.
I'm using it in 0.13 with no problems. The problem is probably reapp specific or maybe because of react context
Thanks for confirming @nmn, I'll leave it to @natew to look into further in reapp if it keeps happening, closing unless we can identify a problem specific to this module.
@JedWatson I'm sorry I made a mistake. I'm using it on 12.2. Not 0.13 please re-open the issue. Sorry for the confusion.
Ha, ok, no problem :)
That said, in the case of 0.13, this should really be implemented in the way of a higher order component (replacement for mixins)
Described here: https://gist.github.com/sebmarkbage
It should need minimal code change.
Can't reproduce this issue across multiple implementations, may be related to some other usage of context in reapp. Closing.
FYI I got this error using react-tappable@0.2.5
with react-router@0.13.3
. The error occurred when I implemented a <Tappable>
in JSX and seemed to stem from react-router/Transition
module. Updating to react-tappable@0.5.1
fixed the problem for me.
Thanks for the confirmation @wmyers, glad to know it's been resolved.
Just tried this in the reapp demo, and when I attempt to use the tag I get this. Figured I'd open this to see if you had any idea before I dug in.
I get this super long stack trace (and slowdown in the devtools):