-
-
Notifications
You must be signed in to change notification settings - Fork 120
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
[FEATURE] : Changing from lucide-react to other alternative icon library #471
Comments
can I work on this issue sir..? |
no need to raise seperate pr for this. will be implemented in #469 if approved |
@TenzDelek i think using an icon library is a bit redundant for us, as we are not using a lot of them. I think using the SVG of this icons in the /illustration will be ideal, don't you think? |
Agree with you, will raise a pr soon. Should we consider removing the icon library(as it will be un used) or keep it for the future sake. |
Why do we need this improvement?
currently we are having lucide react as our icon library. we are only implementing at only one place

currently I am implementing this #469 and was trying to use the lucide react icon for socials like github and all but it turns out that they have deprecated those

in light of all this limitation, I am prosposing to replace lucide and use other alternative like react icon which have a diverse set of icon compare to lucide and heroicon.
would love to hear from @AceTheCreator , @ashmit-coder about this changes.
How will this change help?
more set of diverse icon
Screenshots
No response
How could it be implemented/designed?
npm
🚧 Breaking changes
Yes
👀 Have you checked for similar open issues?
🏢 Have you read the Contributing Guidelines?
Are you willing to work on this issue?
Yes I am willing to submit a PR!
The text was updated successfully, but these errors were encountered: