Releases: csandman/chakra-react-select
Releases · csandman/chakra-react-select
4.0.0-rc.2
What's Changed
- Fix the types being built by removing "increcemental" from tsconfig by @csandman in #124
- In 4.0.0-rc.1 the types were not being published with the package, now they are.
Full Changelog: v4.0.0-rc.1...v4.0.0-rc.2
3.3.6
3.3.5
What's Changed
- Move all Chakra UI packages from
peerDependencies
todependencies
in 78461eb- This is to fix a conflicting peer dependency issue that arose since the release of Chakra UI v2. It also mirrors the change already made in v4.0.0-rc.1.
- This will hopefully prevent any issues from arising with peer dependencies not being installed as mentioned in #78
- This is also how these "peer" dependencies are handled in each of the Chakra UI packages
- As long as you are on a compatible version of
@chakra-ui/react
, each of these dependencies will be de-duplicated during install
Full Changelog: v3.3.4...v3.3.5
4.0.0-rc.1
What's Changed
This is a test release for @chakra-ui/react@2
. If it is stable it will be published as a full release. If you want to test it, you will need to update to @chakra-ui/react@2
and react@18
+ react-dom@18
and follow Chakra's migration guide. When a full release is published the docs will be updated accordingly. A branch for chakra-react-select@3
will be maintained for the time being with any maintenance required for pre-chakra v2 being published to chakra-react-select@3.x
.
- Chakra UI v2 by @csandman in #120
- Update all packages to Chakra UI v2 versions
- Move all chakra packages to
dependencies
frompeerDependencies
- This will hopefully prevent any issues from arising with peer dependencies not being installed like mentioned in #78
- This is also how these peer dependencies are handled in each of the Chakra UI packages
- As long as the user is on a compatible version of
@chakra-ui/react
, each of these dependencies will be de-duplicated during install
Full Changelog: v3.3.4...v4.0.0-rc.1
3.3.4
What's Changed
Behind the Scenes
- Update
babel.config.js
to closer match Chakra UI's - Update
tsconfig.json
to closer match Chakra UI's - Clean up
package.json
- Add a new
format
script - Add new tags
- Downgrade react dev dependencies to match this version of chakra
- Update remaining dev dependencies
- Add a new
Full Changelog: v3.3.3...v3.3.4
3.3.3
What's Changed
- Add
@emotion/react@^11.8.1
as a peer dependency by @csandman in #115- See the PR Description for more information
Full Changelog: v3.3.2...v3.3.3
3.3.2
3.3.1
What's Changed
- ChakraStylesConfig generic default fix by @csandman in #89
- Change the default value for the
IsMulti
generic on theChakraStylesConfig
interface to beboolean
instead offalse
- This is to fix any type errors from using the
isMulti
prop along with aChakraStylesConfig
object - This was made in response to #88
- This is to fix any type errors from using the
- Change the default value for the
Full Changelog: v3.3.0...v3.3.1
3.3.0
What's Changed
- Public
useChakraSelectProps
hook by @csandman in #86- Export the
useChakraSelectProps
hook publicly - Add documentation on how to use the
useChakraSelectProps
hook
- Export the
Full Changelog: v3.2.0...v3.3.0
3.2.0
What's Changed
- [ImgBot] Optimize images by @imgbot in #76
- New
react-select
version + Minor tweaks by @csandman in #84- Update
react-select
to5.3.0
- Update all dev dependencies
- The
isReadOnly
andisRequired
props will not be forwarded from a wrapping form control to the<input>
component- Only
aria-required
is added to the input, as it will not actually be filled when submitting a form so it should not block the submission when it is blank
- Only
- Add the
class-name-prefix--has-value
class to theSelectContainer
component when there is a value selected
- Update
Full Changelog: v3.1.2...v3.2.0