You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since #1707, granular imports are now supported. This is great, but it can become tedious to browse all the existing components, check the imports, and rewrite them manually.
It also clutters the imports, and IDEs tend to auto-import the unoptimized version instead of the right one.
Moreover, in larger projects, it is easy for an inexperienced contributor to accidentally use the old global import. You only need one such mistake to slow down your entire project again.
I just stumbled upon a solution that solves that: preprocessors. The phosphor-svelte community package offers one because this library suffers from the same problem Lucide does. This solution is the best of both worlds: it's transparent to the user, does nothing if the right syntax is already used, and brings the performance gains to codebases of every size for relatively no cost.
It's even potentially expandable to every single Vite-based framework, though for the moment I'd focus on Svelte.
My request is: are you okay with me submitting this subpackage (lucide-svelte/preprocessor) in a PR?
Use cases
Every single Svelte project, especially the largest ones. Potentially expandable to every Vite-based framework.
Checklist
I have searched the existing issues to make sure this bug has not already been reported.
The text was updated successfully, but these errors were encountered:
Package
Description
Since #1707, granular imports are now supported. This is great, but it can become tedious to browse all the existing components, check the imports, and rewrite them manually.
It also clutters the imports, and IDEs tend to auto-import the unoptimized version instead of the right one.
Moreover, in larger projects, it is easy for an inexperienced contributor to accidentally use the old global import. You only need one such mistake to slow down your entire project again.
I just stumbled upon a solution that solves that: preprocessors. The
phosphor-svelte
community package offers one because this library suffers from the same problem Lucide does. This solution is the best of both worlds: it's transparent to the user, does nothing if the right syntax is already used, and brings the performance gains to codebases of every size for relatively no cost.It's even potentially expandable to every single Vite-based framework, though for the moment I'd focus on Svelte.
My request is: are you okay with me submitting this subpackage (
lucide-svelte/preprocessor
) in a PR?Use cases
Every single Svelte project, especially the largest ones. Potentially expandable to every Vite-based framework.
Checklist
The text was updated successfully, but these errors were encountered: