React-motion: React 15.0 support?

Created on 6 Apr 2016 · 12Comments · Source: chenglou/react-motion

It's already RC2: https://facebook.github.io/react/blog/2016/03/16/react-v15-rc2.html

enhancement

Source

sompylasar

Most helpful comment

1.0.0 will have to wait because I want to get static, single component unmounting in (unmount for Motion, which is a large use-case of people doing unmounting animation). Tracked in #311

chenglou on 20 Apr 2016

👍3

All 12 comments

Should not be a problem I am pretty sure, since there are no deprecated APIs being used...

PR to peerDependencies if you are keen (well, with good amount of testing of course) and we should be good then.

    "react": ">=0.13.2 || ^0.14 || ^15.0.0-rc",

nkbt on 6 Apr 2016

If not, I am going to update it in next days (when I will actually work on UI animation on my current project)

nkbt on 6 Apr 2016

@nkbt Thanks! For now I have to delay the upgrade to React 15.0 on my project because a lot of modules haven't updated their dependencies yet, so it would be nice if you have such opportunity with react-motion earlier.

sompylasar on 6 Apr 2016

@sompylasar We updated to 15-rc1 as soon as it came out. Had no issues at all. All other modules simply throw PEERINVALID error on npm install but work totally fine.

I reckon it must depend on what sort of 3rd party modules you rely on, and if some declare React as dependency or rely on deprecated features - then 😿

nkbt on 6 Apr 2016

@nkbt I see, well, I tend to avoid the warnings, they are there for a reason, even if they can be tolerated and everything looks fine at first sight.

I'll give it some time to settle, and get back to it, probably there will be RC3 at that moment, or even a release version -- who knows. react-redux, for example, has strictly specified 15.0.0-rc.1, so I can't use the 15.0.0-rc.2 without the warning, although the latter has several major bugs fixed.

sompylasar on 6 Apr 2016

We should just PR to every lib we use hehe ;)

nkbt on 6 Apr 2016

Reopen until new version published

@chenglou can you please release new patch version (since it is 0.x.x now)?

nkbt on 16 Apr 2016

Will do it this weekend. Time to come back to this.

chenglou on 16 Apr 2016

👍3

Maybe worth going full semver and publish 1.0.0? ;)

nkbt on 20 Apr 2016

1.0.0 will have to wait because I want to get static, single component unmounting in (unmount for Motion, which is a large use-case of people doing unmounting animation). Tracked in #311

chenglou on 20 Apr 2016

👍3

Published as v0.4.3. Also I have no idea how semver works but hey, no breaking changes!

Sorry for the long wait everyone!

chenglou on 20 Apr 2016

Awesome, thanks!
On Wed, 20 Apr 2016 at 17:26, Cheng Lou [email protected] wrote:

Published as v0.4.3. Also I have no idea how semver works but hey, no
breaking changes!

Sorry for the long wait everyone!

—
You are receiving this because you modified the open/close state.

Reply to this email directly or view it on GitHub
https://github.com/chenglou/react-motion/issues/317#issuecomment-212284438