This release adds support for date-fns v3. Thank you @christopherklint97 (#265) and everyone who helped test and fix the beta releases.
BREAKING CHANGES
date-fns v2 is no longer supported
Renamed utcToZonedTime to toZonedTime to make the name less confusing, just search & replace
Renamed zonedTimeToUtc to fromZonedTime to make the name less confusing, just search & replace
All functions are now exported using named exports, this requires changing direct
imports from import formatInTimeZone from 'date-fns-tz/formatInTimeZone' to import { formatInTimeZone } from 'date-fns-tz/formatInTimeZone'
Functions now don’t check the number of passed arguments, delegating this task to type checkers similar to date-fns v3
Arguments are not explicitly converted to the target types; instead, they are passed as is, delegating this task to type checkers similar to date-fns v3
IE is no longer supported since date-fns no longer supports it
Removed flow support since date-fns also removed it
Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.
All Depfu comment commands
@depfu rebase
Rebases against your default branch and redoes this update
@depfu recreate
Recreates this PR, overwriting any edits that you've made to it
@depfu merge
Merges this PR once your tests are passing and conflicts are resolved
@depfu cancel merge
Cancels automatic merging of this PR
@depfu close
Closes this PR and deletes the branch
@depfu reopen
Restores the branch and reopens this PR (if it's closed)
@depfu pause
Ignores all future updates for this dependency and closes this PR
@depfu pause [minor|major]
Ignores all future minor/major updates for this dependency and closes this PR
@depfu resume
Future versions of this dependency will create PRs again (leaves this PR as is)
Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ date-fns-tz (2.0.0 → 3.0.1) · Repo · Changelog
Release Notes
3.0.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 57 commits:
3.0.1
3.0.1-beta.0
Fix typings script to use named exports
Merge pull request #277 from brettwillis/master
fix: Named export typings for V3
3.0.0
Merge pull request #273 from marnusw/version3
v3 release notes
3.0.0-beta.6
Fix ESM import paths
3.0.0-beta.5
Fix ESM import paths
3.0.0-beta.4
Remove redundant step from package.sh
Export all functions using named exports
Remove flow support
Rename to toZonedTime and fromZonedTime
3.0.0-beta.3
Add convertToFP from date-fns
3.0.0-beta.2
Merge pull request #272 from gugu/patch-1
copy tests
inline getTimezoneOffsetInMilliseconds
3.0.0-beta.1
Correct various date-fns@v3 imports
Merge pull request #271 from gugu/patch-1
add webpack babel handler to mjs files as well
Remove prepare script because it does not help to install the module from github directly
Add prepare script
Correct import of date-fns@v3 format
3.0.0-beta.0
Merge pull request #265 from christopherklint97/update-to-v3
Merge branch 'master' into update-to-v3
2.0.1
Yarn 4.1.1
Clean up after merging #247
Merge pull request #247 from asennikov/master
Merge pull request #270 from millawell/master
Merge pull request #267 from drewbrend/patch-1
Merge pull request #254 from TheThing/patch-1
Merge pull request #231 from Semigradsky/fix-230
Merge pull request #229 from anikeef/fix-0030-timezone
Fix incorrect output comment
Update yarn.lock
cleanup package.json
fix types and xit some tests
add clonedeep as dependency instead of devDependency
fix babel-loader
Update date-fns to v3
lock `date-fns` to 2.x
tzTokenizeDate: Remove weird unneeded regex
improve correctness of formatInTimeZone close to DST threshold
fix: Use `hourCycle` for browsers that support hour cycle formatting
Add test cases for 00:30 timezones
Update index.js
Merge pull request #226 from PCOffline/patch-1
docs: fix typo in 2.0.0 release changes
Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase
.All Depfu comment commands