croqaz / later-again

🚧 Library for defining recurring schedules and calculating future (or past) occurrences
MIT License
7 stars 1 forks source link

Project direction #1

Open miguelocarvajal opened 6 years ago

miguelocarvajal commented 6 years ago

Hello!

Ran across your project as I am searching for a solution to the later.js project being dead.

Are you looking to keep the API compatible with the current later.js?

I ask because I see you're looking into using Luxon or Dayjs. Luxon I am somewhat familiar with because of moment.js and I know they have bundle size issues (see https://github.com/moment/luxon/issues/94). Which is why we use date-fns, in order to better support tree shaking. I have no information on Dayjs although they seem to be big on a small bundle size.

We have not started using Later.js yet but will need a solution now. Which is why we may start using it right away and if this project aligns with what we're doing, we may be able to contribute to get a maintained and more up to date solution.

Let me know!

croqaz commented 6 years ago

Hi @miguelocarvajal !

The status of the project for now is: unmaintained. I want to finish it someday, because I really need this kind of library and I didn't find anything that's coming even close to that later.js is doing.

I got stuck at /core/compile and /core/schedule, there are so many things to do there... All the folder /units/ must be converted to use Luxon, or Dayjs, or whatever. Maybe this folder can be eliminated completely. It's a pretty big and complicated library.

Feel free to copy & paste this code and work on your own repo, or create a fork and work here. I will check all PRs and we can go from there. Whichever you prefer.

I will take a look at date-fns.

Thanks !