Proposal to implement Svelte port

[JaViLuMa]

I really love how simple it is to use and how customizable this package is.

Professionally, this is my go-to library for anything that includes working with calendars. That's why I would love to help create/implement a Svelte version of this package or at least give the idea of there existing Svelte version.

[gpbl]

@JaViLuMa i'd love to see a Svelte port of DayPicker. What could be the next step here?

Source is MIT-licensed, so I'm sure there's a legit way to reuse the code via copy/paste :)

On the other side, what if someone else wants to implement t a Vue version? I'm thinking about further abstracting DayPicker internals in a React-free module, for easier reuse by other libraries. This may help solidifying the code behind DayPicker, but poses multiple challenges.

---

What about packages like:

daypicker/core
daypicker/react
daypicker/svelte
daypicker/vue 

/cc @rodgobbi - what are your thoughts here? Could it be a step too big for the next future?

[JaViLuMa]

As you mentioned, we could definitely make parts of the package framework agnostic. The proposed package structure would be amazing (monorepo could be useful here in this case I believe).

And also one of the steps would be to rewrite React specific code into framework specific code (like components/hooks that rely on context/state/effect etc...).

As for licensing, I am not completely familiar with MIT license restrictions, but all credit would be kept and given 😄

[gpbl]

Yes looking at the hooks, they don't seem too much react-dependent. Feel free to try your port, let us know how it goes and if restructuring some of DayPicker internals could help.

[JaViLuMa]

Then even better! 😄

And will do! I am looking forward to it!

I will also write down which parts didn't require changing/rewriting so maybe in the future it can help when making a core package