react-timezone-select

• Fix: "use client" injection

Full Changelog: https://github.com/ndom91/react-timezone-select/compare/v3.2.2...v3.2.3

• Fixed timezone fuzzy match scoring - https://github.com/ndom91/react-timezone-select/issues/115

Full Changelog: https://github.com/ndom91/react-timezone-select/compare/v3.2.1...v3.2.2

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

Full Changelog: https://github.com/ndom91/react-timezone-select/compare/v3.2.0...v3.2.1

• Add new prop - currentDatetime - allow overriding "current" time
  • Thanks @gflores-jahia! (https://github.com/ndom91/react-timezone-select/pull/113)

• 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

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

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

• Fixes daylight savings time abbreviations and altnames for TZ's that don't observe DST (See: https://github.com/ndom91/react-timezone-select/pull/96)

• 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.

• Bumped timezone-soft and spacetime versions
• Gracefully handle timezones not found by those libraries

• Update bundling / distribution
• No longer publishes react/react-dom/emotion, etc. per default with the library

PR: https://github.com/ndom91/react-timezone-select/pull/82

Full Changelog: https://github.com/ndom91/react-timezone-select/compare/v1.5.0...v1.5.1

Changes

• Small TS fix

Notes

• https://github.com/ndom91/react-timezone-select/pull/89
• https://github.com/csandman/chakra-react-select/discussions/252

• Bumped react-select to 5.7.0

Changes

• Fixed the ESM/CJS bundling issue. You no longer need next-transpile-modules to use this library with Next.js 12+.

• Improved typescript types / exports
• Removed css module for hover styling, was blocking use in next.js

This release doesn't strictly provide new features, but I did upgrade all of the dependencies behind the scenes and renamed one rarely used export.

Changes are as follows:

• spacetime-informal was renamed to timezone-soft
• react-select: 4.3.1 -> 5.0.0
• spacetime: 6.16.2 -> 6.16.3

The timezones object export was renamed from i18nTimezones to allTimezones. This is only there for those that want to extend the list of available timezones themselves, and then spread this list of existing timezones in to fulfill the list.

There were also some minor internal typescript changes that should not affect the end use of this component.

Hey yall!

If you haven't checked in here in a while, this is a major version bump, but no user facing breaking changes!

Just figured its finally time for a major version bump as there have been a lot of internal changes, including:

• tip: can select the users local timezone by default (...useState(Intl.DateTimeFormat().resolvedOptions().timeZone)) - see readme for details
• automatically match all possible timezones from the above ^^ to the matching selection available in the dropdown
• rewrite in typescript ✨
• pure esm package (if you're having trouble with next.js because of this - check the readme for a workaround 🎉)
• rewrite / reorganisation of the included demo / dev env app

To get up and running, just install from npm and follow the instructions in the readme!

npm install react-timezone-select

Thanks for your interest and support thusfar!

Some major changes have taken place since the last stable release. I've refactored the component to be in Typescript, so those of you looking for types, they are now included! Of course you can still use it as you have always been in normal javascript as well. There is no breaking-change in this regard.

In fact, we've also added jest and a suite of tests to ensure there are no unintended breaking changes going forward!

Added package.json attributes for import/export to better support usage as an ESM Module.

This is a smaller release which redefines how we parse the value passed into value.

It now allows, for example, to simply pass in the timezone name (i.e. "Europe/Berlin") if thats all you store in your DB, and it'll find the correct timezone object and use it.

Thanks #11 for the issue / suggestion!