[BUG] peerDependencies to Chakra v2 still show up about chakra-react-select HOT 5 CLOSED

I'm confused what you mean by this, if you look at the description in the docs, it does specifically say Charka v2:

This version of chakra-react-select is updated for Chakra UI v2 which works exclusively with React v18. chakra-react-select v3 will be maintained until the majority of users have migrated. If you're still using Chakra UI v1 check the docs for chakra-react-select v3 here.

Maybe you're getting confused by my distinguishing v3 of this package? Chakra UI (specifically the combined React package) doesn't even have a v3 yet.

If you're talking about the warnings, those can be safely ignored. As long as you have the proper version of @chakra-ui/react installed, this package will use the packages installed by that. Overall this package could be using @chakra-ui/react as it's direct peer dependency, but I had switched this a while ago based on this discussion: #56

I've been considering going back to using the top level package recently though.

from chakra-react-select.

Sorry, you are perfectly right. I got confused with the versions and was assuming a v3, which is not there, because of those warnings.

However, when I checked the installed packages, they are all there in the required versions. So, why do they still show up as warnings? Ir is that another inconsistency with yarn v1 and workspaces?

from chakra-react-select.

They show up because they're dependencies of @chakra-ui/react and not direct dependencies of your project. It is something I have noticed specifically with yarn though, as I haven't seen these warnings with NPM >= v7 (or maybe it's v6).

from chakra-react-select.

That's fine for me. It's not this library, but yarn. You may close this bug.

from chakra-react-select.

Cool, glad you got it figured out!

from chakra-react-select.