You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The reason will be displayed to describe this comment to others. Learn more.
Just out of interest, is there anything in particular I need to look out for when using react-responsive alongside react@^15.0.0?
I'm using your lib alongside gatsby which at the current version hasn't been updated to require v16 of react. Looking at your commit message, it appears that this change was just a routine change to keep everything up to date (which is fine - I can just ignore the warning until gatsby catches up) I was just wondering if there was a particular issue this resolved.
0436fb5There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just out of interest, is there anything in particular I need to look out for when using react-responsive alongside react@^15.0.0?
I'm using your lib alongside gatsby which at the current version hasn't been updated to require v16 of react. Looking at your commit message, it appears that this change was just a routine change to keep everything up to date (which is fine - I can just ignore the warning until gatsby catches up) I was just wondering if there was a particular issue this resolved.
Gary
0436fb5There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@gsteinert 4.0 relies on react 16 fragments, you can use 3.0 with react 15 just fine - no feature differences.