Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TZDateMini recommendation is impractical #20

Open
camsteffen opened this issue Oct 4, 2024 · 0 comments
Open

TZDateMini recommendation is impractical #20

camsteffen opened this issue Oct 4, 2024 · 0 comments

Comments

@camsteffen
Copy link

From the readme:

Even though TZDate has a complete API, developers rarely use the formatter functions outside of debugging, so we recommend you pick the more lightweight TZDateMini for internal use. However, in environments you don't control, i.e., when you expose the date from a library, using TZDate will be a safer choice.

This made me think I ought to use TZDateMini in my app since I have full control over how date objects are used (as is the case for many apps). The problem is that, if I use { in: tz(..) } anywhere in the app, I will end up depending on TZDate and thus lose out on any benefit of using TZDateMini. So, unless I'm missing something, TZDateMini seems impractical for most use cases.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant