v3.1.0

What's new?

• Added support for React 18.

v3.0.0

❗️ = breaking change

What's new?

• React-Clock now ships with ES6 Modules along with CommonJS modules. This allows for Webpack and other bundlers to optimize your code better.

What's changed?

• ❗️ React-Clock no longer imports its styles by default. If you want to continue to use them, import them separately as instructed in README.

v3.0.0-beta

❗️ = breaking change

What's new?

• React-Clock now ships with ES6 Modules along with CommonJS modules. This allows for Webpack and other bundlers to optimize your code better.

What's changed?

• ❗️ React-Clock no longer imports its styles by default. If you want to continue to use them, import them separately as instructed in README.

v2.4.0

What's new?

• Added TypeScript typings.
• Added more unit tests.

What's changed?

• React-Clock now uses Babel 7 internally.
• Rewrite for optimal Babel output, resulting in ~25% bundle size savings.

v2.3.0

What's new?

• You can now render numbers on the clock using renderNumbers prop (#6). Thanks, @yhlben!

Bug fixes

• Fixed negative percent values for oppositeLength props throwing React warning. Thanks, @bjenkins24!

v2.2.1

What's new?

• Refactored code for enhanced stability and readability.

Bug fixes

• Fixed a configuration bug that could have caused React-Calendar to behave unexpectedly on React 15.x environments.

v2.2.0

What's new?

• Compiled files are now placed in a standard ./dist category.
• Added unit tests.
• Sample and Test suites are now using Parcel for bundling.
• Updated development platform:
  • Updated Jest to version 22.
  • Replaced babel-preset-es2015 with babel-preset-env.

v2.1.0

What's new?

• You can now pass values as string, e.g. "11:20:38".

Bug fixes

• Fixed a styling issue that could have caused React-Clock not to be rendered

v2.0.1

Bug fixes

• Fixed Clock.css file missing from build folder.

v2.0.0

React-Clock is now on NPM and Yarn! 🎉

As React-Clock name was previously used by another library, to avoid confusion, versioning had to be aligned with preexisting npm package.