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
More just reporting some research than a feature request.
lucide-svelte exposes each icon as a Svelte component. If you want to support it in a way that works with the Icon component, the plain lucide package is more similar to how FontAwesome works, though still different enough that it would still require new code paths.
In the lucide package, each icon is a 3-element array. The first element is the tag name to use (I assume always svg? But haven't looked).
The second element is the attributes to put on the tag. I haven't looked enough to see how much these tend to differ.
The third element is an array of the SVG elements to use. As you see in the example below from the User icon, this is not always a path.
It's theoretically possible that these can be recursive, and something like a <g> could be represented in the 3rd element by ["g", {}, [ subelements ] ]. But I haven't seen that occur in a brief perusal of the package, and given the relative simplicity of the icons here I wouldn't expect it.
The text was updated successfully, but these errors were encountered:
Related: #267
More just reporting some research than a feature request.
lucide-svelte
exposes each icon as a Svelte component. If you want to support it in a way that works with theIcon
component, the plainlucide
package is more similar to how FontAwesome works, though still different enough that it would still require new code paths.In the
lucide
package, each icon is a 3-element array. The first element is the tag name to use (I assume always svg? But haven't looked).The second element is the attributes to put on the tag. I haven't looked enough to see how much these tend to differ.
The third element is an array of the SVG elements to use. As you see in the example below from the
User
icon, this is not always apath
.It's theoretically possible that these can be recursive, and something like a
<g>
could be represented in the 3rd element by["g", {}, [ subelements ] ]
. But I haven't seen that occur in a brief perusal of the package, and given the relative simplicity of the icons here I wouldn't expect it.The text was updated successfully, but these errors were encountered: