Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Support for react v15.0
See original GitHub issueReact 15 has nice performance enhancements and better svg support. I imagine sparklines probably works with it, but it would be nice to bump support up if it is fully compatible.
Issue Analytics
- State:
- Created 7 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
React v15.0 – React Blog
As usual with major releases, React 15 will remove support for some of the patterns deprecated nine months ago in React 0.14. We...
Read more >React v15.0 Release Candidate
This 15.0 release follows our previous 0.14 version and we'll continue to follow semver like we've been doing since 2013. It's also worth...
Read more >React v15.5.0 – React Blog
React v15.5.0 ... To that end, today we're releasing React 15.5.0. ... We're also discontinuing support for the react-with-addons UMD build.
Read more >React v15.4.0 – React Blog
In React 15.4.0, we are finally moving React DOM implementation to the React DOM package. The React package will now contain only the...
Read more >React v15.0 Release Candidate 2
React v15.0 Release Candidate 2. March 16, 2016 by Paul O'Shannessy. Today we're releasing a second release candidate for version 15.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
It should work in master, but not the version published to npm. Could you publish a new version to npm? Thanks!
I did publish a version with dependencies of version ‘*’. Lets see if that works.