-
Notifications
You must be signed in to change notification settings - Fork 18
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
Plans for date-fns v2? #4
Comments
Thanks for the warn words, @motin! I use only public interface of I intend to maintain this library for both v1 and v2. v2, once I get my hands on it :-) I'll consider opening a PR for date-fns/date-fns#707 takes a different approach - it uses the native I integrated |
V2 is out now and its |
any updates on this? is v2 support planned? do you need any help? or is this project done? |
I'm still on |
Looks like this project is unmaintained? no activity for a year |
looks like it. I recently upgraded to date-fns 2x in a project and just extracted and build the stuff I needed by myself... :( |
@ngehlert Got anything you can PR? |
Wait wait wait, did v2 make this library unnecessary? https://date-fns.org/v2.16.1/docs/Time-Zones |
@jkeen That library requires the browser to support parts of |
@erikt9 Ahh is that all? That helps me out, because my app doesn't support IE. Thanks! |
Great job in making it possible to work with timezones using date-fns v1! How well does this work with date-fns v2 alpha currently? Will this library live on after v2 release or deprecated once v2 is available and date-fns/date-fns#707 is merged? Or will you port your changes to a new PR for v2?
The text was updated successfully, but these errors were encountered: