Update React Native peerDependency

[Rovack]

It's been 2 months since React Native 0.44 was released, and they just now released stable version 0.46.
However, storybook/react-native's peerDependencies to this day remain "react-native": "0.27.0 - 0.43.x".

I don't know if there's anything that would actually prevent this module from working with React Native 0.45 or 0.46, but at the very least I've personally used it with 0.44.0, and it seems to work fine (granted, I can't be sure I've covered all cases).

Of course, this is only a peerDependency, and theoretically it shouldn't stop anyone from using Storybook with a newer version of React Native, but unfortunately that's not the case for any project still relying on shrinkwrap.
As it stands, shrinkwrap refuses to update as long as a peerDependency is unmet (see here and here), and it doesn't look like that's about to change anytime soon.

So, 2 months later, it might at least make sense to try updating the peerDependency to something like "0.27.0 - 0.44.x".

[ericwooley]

It could probably be set too ^0.27.0

Not sure why they did it the way they did.

[atticoos]

Prereleases are treated specially by semver and an explicit range or >= is required to satisfy these types of matches.

See an example here:

At the very least, it sounds like we're overdue to update the upper bound of the range. Perhaps we can consider >=0.27.0 to have an opened upper bound with the expectation that there can be breaking changes ahead. Not sure if want to have that open-ended range though.

I could see it working, for example, say we can safely use react-native between 0.27.0 and "current":

"react-native": ">=0.27.0"

Later down the line, say at 0.50.0, let's say there's a new breaking change and we must have a new minimum of 0.50. We could just update that peer dep and continue keeping it open-ended

"react-native": ">=0.50.0"

[smooJitter]

Nope, it does not work work .45.1

[rmevans9]

@smooJitter what are you not seeing work in 0.45.1? I have it working perfectly fine in 0.46.4

[atticoos]

I think we can close this issue to the original point of latest ReactNative releases being blocked by peerDependencies, now that #1424 has been merged.

There are some dependency issues as of 3.2.0 outlined in #1553, but that should be something we can provide a backward compatible solution for without needing to set a minimum dependency version.