5.0.2

What's Changed

Mostly some documentation/CI changes, along with a new build config.

• feat: Add a demo vite app by @csandman in #344
  • Added a new local demo app for testing. See the Contributing doc for more info.
  • Added a new build action for previewing PR changes.
• Improve the exports and modify the tsup build config by @csandman in #346
  • Update exports to include specific types paths for import and require.
  • Changed build config to stop minifying the output and building source maps.

Full Changelog: v5.0.1...v5.0.2

5.0.1

What's Changed

• Removes support for the isFixed attribute on options to remove the tag close button. This was supposed to be removed with the other breaking changes, but it was missed.
  • The original idea for this feature was taken from an example in the react-select docs for how you can use custom components. Because of this, this should be done by the end user if desired.

Full Changelog: v5.0.0...v5.0.1

5.0.0

What's Changed

This is the last major release before Chakra v3 is fully released! The intention of this release is to batch a few breaking changes that have been in the works for a while, along with a codemod to hopefully make the changes for you.

Breaking Changes

1. The useBasicStyles prop was removed, as the styles provided by it are now the default. Originally, it was styled to match the InputRightAddon component, in order to create a visual separation between the dropdown indicator and the clear indicator. However, it seems that most people preferred it to visually match the original Chakra Select component, so those styles are now the default. If you want to modify the styles to appear like they used to, you can do so using the chakraStyles prop. Some examples of how to do this are provided in the README.
2. Remove the deprecated selectedOptionColor prop. A new prop was added a while ago to replace that one, selectedOptionColorScheme, as some people were getting confused by the meaning of the original (thinking it meant an explicit color instead of a named color from their theme). The old one was left in the code though, and now it is gone for good.
3. Remove the deprecated hasStickyGroupHeaders prop. This was removed from the documentation since v4.6.0, as it was only ever really an experimental way to style the grouped option headers so they'd stay in view while you scroll the list of options. It also had some problems with using the keyboard to navigate between options. They would disappear behind the header when you used the up arrow. There is an example for how these styles can be implemented using chakraStyles in #343.
4. Renamed the colorScheme prop to tagColorScheme. There has been some confusion around what this prop actually means, as the original name the prop had wasn't specific enough to it's purpose. It didn't make sense to have a specific prop for selectedOptionColorScheme, and not be specific with the naming for the tagColorScheme. This may be followed by the addition of a new root colorScheme prop, but that isn't included here.

All of these changes can be made automatically using the Codemod provided here

npx crs-codemod@latest v5 .
# or
npx crs-codemod@latest v5 ./src

---

This release will most likely mean an end of support for v3 (Chakra v1 compatible version), unless people want to put up any fix PRs for it themselves.

Full Changelog: v4.10.1...v5.0.0

4.10.1

What's Changed

• fix: Reduce selected menu option styles specificity by @csandman in #338

Full Changelog: v4.10.0...v4.10.1

4.10.0

What's Changed

• fix: Switch peer dependencies to depend on @chakra-ui/react instead of sub-packages by @csandman in #336

Full Changelog: v4.9.2...v4.10.0

4.9.2

What's Changed

• fix: Change package type back to default of "commonjs" by @csandman in #331
  • This was to fix #329, which was being caused by Jest importing the wrong build of the package.

Full Changelog: v4.9.1...v4.9.2

4.9.1

What's Changed

• fix: Fix react-select core Props type export by @csandman in #324

Full Changelog: v4.9.0...v4.9.1

4.9.0

What's Changed

• chore: Switch to tsup for building and update dependencies by @csandman in #298
  • This change should finally make this package fully support ESM, where as before it didn't really which was causing some issues. It should fix an issue with the ID prop not matching mentioned in #260, without the need for a workaround. Check the PR description for full details!

I tested this change in a few different environments with different module resolution setups but it's possible I missed a case. If it ends up not working for your particular setup, please open a bug report with as much specific information as you can give me, such as:

• Chakra Package Versions
• React Version
• TypeScript or Vanilla
• Yarn or NPM (and which version of the package manager you're on)
• Your jsconfig/tsconfig setup

I'm not likely to figure out what's going on if I can't replicate the environment locally, so the more information you can provide the better!

Full Changelog: v4.8.0...v4.9.0

4.8.0

What's Changed

• chore: Update all dependencies by @csandman in #315
  • This introduces [email protected] which improves the native accessibility.

Full Changelog: v4.7.6...v4.8.0

3.3.10

What's Changed

• Fix for V3: Prevent a selected option from being removed when isDisabled is passed by @lschlesinger in #302

New Contributors

• @lschlesinger made their first contribution in #302

Full Changelog: v3.3.9...v3.3.10