-
Notifications
You must be signed in to change notification settings - Fork 935
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
Support react 0.14.0-beta3 #102
Comments
#100 I think you could still using it. |
Perhaps removing the dependency from package.json might be enough. When I tried upgrading the dependency in a fork I had these errors though, and it didn't work. Have you tried with beta3 instead of just beta1? |
@boosh I'm using this fork for the moment without any errors : https://github.com/VonD/react-google-maps/tree/no-peer-dependency |
@VonD you're awesome! |
Hmm I get an error when I copy and paste the simple map example into my project with that branch:
When I installed it, it complained about needing react 0.13 but it not being installed... In 0.14 they've split the DOM stuff out of core, so perhaps this is the problem? |
Yeah. I still had problems with it for some reason. |
@boosh is by any chance react installed in the node_modules directory of the react-google-maps package ? |
2.5.1 |
I was using 3.0.0 but I've downgraded. I'll test it when I get chance. |
If you use 3.0.0. npm will flatten your dependencies into the top most |
I'd do this myself but I'm a react noob... I'm getting errors about the import of
findDOMNode
after upgrading the dependency to react 0.14.0-beta3, and more errors after fixing that import...The text was updated successfully, but these errors were encountered: