Skip to content

Conversation

@joe-castle
Copy link
Owner

No description provided.

Upgraded to latest dependencies. Resolved issues surrounding them.
When providing a date that's in the past (without a backupStartTime, or a backup that's also in the
past) the timer now no longer throws an error and immediatley finishes the timer. This allows for
better handling of non persistent timers.

BREAKING CHANGE: start() no longer throws an error when startTime = 0 with countdown = true.
dateToSeconds also no longer throws an error when startTime or backupStartTime are in the past but
now returns 0.
removed deprecated method from Timr

BREAKING CHANGE: isRunning removed
Re-structured rollup config to make use of output array, rather then individual input/output ojects
Rather then the original custom date parsing, we're now using date-fns/parseISO to be fully
compatible with parsing ISO8601 dates.

BREAKING CHANGE: When passing an invalid date format, e.g. (0000-00-00). Previously an error would
be thrown when it couldn't be parsed with a message starting: 'The provided date is not in the right
format or is incorrect.'. Now it will throw an error with a message: 'Expected time to be in
(hh:mm:ss) format, instead got: 0000-00-00'. This is due to the fact that the parsing logic is
passed over to the timeToSeconds function when a parseISO returns an "Invalid Date".
Update node version in github actions from 15 to 18
@coveralls
Copy link

Coverage Status

coverage: 99.057% (-0.002%) from 99.059%
when pulling 0e811aa on develop
into bfbfbfb on master.

@joe-castle joe-castle merged commit 41131e8 into master Jul 9, 2025
9 checks passed
@github-actions
Copy link

github-actions bot commented Jul 9, 2025

🎉 This PR is included in version 4.0.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants