build(deps): bump lucide-svelte from 0.469.0 to 0.474.0

[dependabot]

Bumps lucide-svelte from 0.469.0 to 0.474.0.

Release notes

Sourced from lucide-svelte's releases.

New icons 0.474.0

Modified Icons 🔨

• expand (#2677) by @​jguddas

New icons 0.473.0

Modified Icons 🔨

• package (#2706) by @​sezze

New icons 0.472.0

New icons 🎨

• battery-plus (#2693) by @​Footagesus
• map-plus (#2697) by @​Seanw265

What's Changed

• lucide-svelte: Make sure license ends up in SvelteKit bundles by @​Lettnald in lucide-icons/lucide#2728
• lucide-react: Fixes aliases imports.

Full Changelog: lucide-icons/lucide@0.471.1...0.472.0

Hotfix Lucide React exports

What's Changed

• fix(lucide-react) Adds type module in package.json by @​ericfennis in lucide-icons/lucide#2731

Dynamic Icon component Lucide React and new icons 0.471.0

New Dynamic Icon Component (lucide-react)

This is an easier approach than the previous dynamicIconImports we exported in the library. This one supports all environments. We removed the examples in the docs of how you can make a dynamic icon yourself with a dedicated DynamicIcon component. This one fetches the icon data itself and renders it instead of fetching the Icon component from the library. This makes it more flexible with all the frontend frameworks and libraries that exist for React.

🚨 Not recommended for regular applications that work fine with the regular static icon components. Using the dynamic icon component increases build time, separate bundles, and separate network requests for each icon.

How to use

DynamicIcon is useful for applications that want to show icons dynamically by icon name, for example when using a content management system where icon names are stored in a database.

const App = () => (
  <DynamicIcon name="camera" color="red" size={48} />
);
</tr></table> 

... (truncated)

Commits

• 27c6675 Make sure license ends up in SvelteKit bundle (#2728)
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud