v3.2.7

What's Changed

• Don't crash on null input
• Hide abbreviations for those timezones that don't have any
• fix: main useMemo, add dependency on currentDatetime by @weissleb in #124
• fix: incorrect type for onChange handler argument by @ndom91 in #120

New Contributors

• @weissleb made their first contribution in #124

Full Changelog: v3.2.3...v3.2.7

v3.2.3

• Fix: "use client" injection

Full Changelog: v3.2.2...v3.2.3

v3.2.2

• Fixed timezone fuzzy match scoring - #115

Full Changelog: v3.2.1...v3.2.2

v3.2.1

• Add "use client" directive for use in applications using server components

Full Changelog: v3.2.0...v3.2.1

v3.2.0

• Add new prop - currentDatetime - allow overriding "current" time
  • Thanks @gflores-jahia! (#113)

v3.1.0

• Ship as ESM only to fix some other import issues
• Bump react-select peer dependency to v5.7.3 as minimum due to their shipping of a node esm import fix

v3.0.2

Summary

Not many changes here, but bumped a major version because I removed a prop (maxAbbrLength) and thats a breaking change.

Changes

• Removed maxAbbrLength prop
• Core code clean-up
• Migrate testing from jest to vitest
• Update example

v2.1.0

• Releases useTimezoneSelect hook to decouple this component from the react-select dependency.
  • PR: #81
  • Docs: https://github.com/ndom91/react-timezone-select#-custom-select-component
  • Thanks @DreierF

v2.0.1

• Fixes daylight savings time abbreviations and altnames for TZ's that don't observe DST (See: #96)

v2.0.0

• Major release simply because the primary dependency (react-select) has been made a peer dependency now, in preparation for releasing a hook for the library, decoupling the functionality completely from the react-select component. If you use npm 7+ it will auto install it peer-dependencies for you. If you use another package manager, you may need to add react-select to your project.