-
Notifications
You must be signed in to change notification settings - Fork 29
Uncaught Invariant Violation: addComponentAsRefTo(...) #114
Comments
Lock passwordless works with React 0.14. I'll schedule some time to perform the upgrade to React 15. |
@gnandretta Any updates on a schedule for React 15 support? |
I get this as well, but on initial launch of the lock |
@luisrudge You need to use React v0.14 for now, since development on this library apparently has stopped. |
We were able to get passed this by externalizing react from the project through webpack |
@ChristianDavis right.. but this won't work with something like nextjs (https://github.com/zeit/next.js) or even create-react-app, since you don't have control of the webpack config |
I think you need to list React as a peer dependency. Loading two different versions of React is always going to lead to this issue. The other option would be to release a different version of auth0-lock-passwordless for each version of React, and asking users to select the lock version matching their react version. |
I'm getting this same issue. |
I'm trying to use
lock-passwordless
in my React application. After signing in using email code and seeing "Thanks for signing in.", this error appears in console:My application is using
[email protected]
. NPM also shows this error:UNMET PEER DEPENDENCY [email protected]
under thelock-passwordless
tree.The text was updated successfully, but these errors were encountered: