Lucide integration out of date or not working

Steps to reproduce

Make a custom callout, try to use a Lucide icon such as this one: Lucide | Lucide

Did you follow the troubleshooting guide? [Y/N]

Not applicable because the bug is directly related to CSS snippets, which is an edge case not handled by the procedure which involves disabling CSS snippets.

Expected result

The icon from Lucide to be used.

Actual result

The icon is not used.

Environment

SYSTEM INFO:
Obsidian version: v1.4.5
Installer version: v1.3.5
Operating system: Windows 10 Home 10.0.19045
Login status: not logged in
Insider build toggle: off
Live preview: on
Legacy editor: off
Base theme: dark
Community theme: none
Snippets enabled: 1
Restricted mode: off
Plugins installed: 1
Plugins enabled: 0

RECOMMENDATIONS:
Custom theme and snippets: for cosmetic issues, please first try updating your theme and disabling your snippets. If still not fixed, please try to make the issue happen in the Sandbox Vault or disable community theme and snippets.


Additional information

.callout[data-callout="custom-callout"] {
    --callout-icon: lucide-swords;
}
2 Likes

The icons Obsidian uses are behind what’s available on the Lucide site.

This looks like the latest post:
https://obsidian.md/changelog/2023-02-16-desktop-v1.1.14/

The Lucide icon library has been upgraded to v0.114.0 meaning there are new icons available to be used.

If there is a good reason for why the Lucide integration is not updated regularly I would love to hear it. I personally think it’s kind of silly.

If they want to continue staying behind, the version number of Lucide should be available on the docs, particularly here:

…rather than me having to jump on a forum and have someone pull up a changelog as the only mention of this discrepancy between versioning of a 3rd party integration.

2 Likes

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.