Version 5.0.0-rc.2

[jamesrweb]

@Qanpi @yevdyko how are you finding the latest rc version?

[yevdyko]

@jamesrweb It works great with React 19, but I still need to test it with 18 this weekend.

As for the version 5 release itself, since the breaking changes are already included, maybe we can improve the component name and make it more suitable such as P5Canvas. After all, we know when we use it that we have the component in the React application as a wrapper over P5, but it would be nice to emphasize that it's built on top of canvas and besides P5 uses the internal class name as P5Canvas for the canvas element.

@jamesrweb @Qanpi What are your thoughts on this?

[yevdyko]

@jamesrweb I tried version 5.0.0-rc2 in the app using React 18.3, and it doesn't work, so the peer requirements >=19.0.0 look relevant: https://github.com/yevdyko/react-p5-wrapper-demo/tree/react-p5-wrapper-5.0.0-rc2

Do we want to add package size optimization to version 4 that supports React 18?

[jamesrweb]

I'd rather leave version 4 as it is since it's stable and "just works" for react 18 as is. WDYT?

We could try to support 18+ for version 5 I suppose but then we need to test it as another rc version. What I don't want though is to release the final version with only partial react 19 support. Should I create an rc.3 with 18+ as a peer dependency? I'm not even sure it's needed to support 18 to be honest, API wise, 19 is 18 but with more stuff, since it's backwards compatible anyway, so if people have to upgrade, it shouldn't be an issue, right? I mean as far as I can see, the 18 to 19 upgrade is pretty simple. I'm still not sure to be honest if it's worth it.

If we have to choose between full react 19 or partial react 19 to support react 18, I think we both agree that's not a worthwhile tradeoff, right?