fix: Switch dependencies to depend on @chakra-ui/react
instead of sub-packages
#336
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR fixes #335 by removing the peer dependencies on the sub-packages of
@chakra-ui/react
and switches to depend on the full package. This is something I've been meaning to do for a while, and already made the change for my upcomingv5
release (#323), as the peer sub-packages have been frustrating to people.As of
@chakra-ui/[email protected]
, this now becomes a required change due to their switching to a single package approach, because the peer dependencies of the individual sub-dependencies are no longer installed at the top level: chakra-ui/chakra-ui#8153Here are some notes one why I wanted to make this change before this breaking change anyway from #323:
In addition to this, I updated all of the other dependencies of this package:
as well as switched to a newer
tsconfig.json
setup based on the tsconfig from@chakra-ui/react
: https://github.com/chakra-ui/chakra-ui/blob/main/tsconfig.build.json