8000 Litepicker is dead? · Issue #2242 · tabler/tabler · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Litepicker is dead? #2242

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

Open
SantosVilanculos opened this issue Mar 25, 2025 · 3 comments
Open

Litepicker is dead? #2242

SantosVilanculos opened this issue Mar 25, 2025 · 3 comments

Comments

@SantosVilanculos
Copy link
SantosVilanculos commented Mar 25, 2025

#1804

The project currently utilizes the 'litepeaker' library, which has been archived since 2023. This poses a potential risk due to lack of maintenance and security updates. You should evaluate and migrate to a supported alternative to ensure project stability and security.

Image

Image

@vjmartins
Copy link

Another option: https://github.com/easepick/easepick/

@ethancrawford
Copy link
Collaborator

I'm not 100% sure where it's used, but flatpickr was added as a dependency by @codecalm as part of #2183. Perhaps it makes sense to go with that one?

@kevinpapst
Copy link
Collaborator

I thought we discussed that before... easepick was developed by the developer, who now archived litepicker.
And it is GPL licensed and therefor "slightly incompatible" with Tablers MIT.
I'd use Flatpickr if nothing better comes up.

A lot of projects likely rely on Litepicker, so removing support from Tabler should probably done slowly.
I'd even recommend an approach, where we keep the CSS rules in a separate file for an easier migration path.

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

4 participants
0