fix(deps): update dependency lucide-react to ^0.474.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
lucide-react (source)	^0.473.0 -> ^0.474.0

---

Release Notes

lucide-icons/lucide (lucide-react)

v0.474.0: New icons 0.474.0

Compare Source

Modified Icons 🔨

• expand (#​2677) by @​jguddas

v0.473.0: New icons 0.473.0

Compare Source

Modified Icons 🔨

• package (#​2706) by @​sezze

v0.472.0: 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 https://github.com/lucide-icons/lucide/pull/2728
• lucide-react: Fixes aliases imports.

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

v0.471.1: Hotfix Lucide React exports

Compare Source

What's Changed

• fix(lucide-react) Adds type module in package.json by @​ericfennis in https://github.com/lucide-icons/lucide/pull/2731

v0.471.0: Dynamic Icon component Lucide React and new icons 0.471.0

Compare Source

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} />
);

Possible Breaking changes

We have switched to the "exports" property in package.json. This can cause issues if you have directly imported scripts from the package. Please open an issue if we need to refine this export map.

New icons 🎨

• triangle-dashed (#​2652) by @​Yohh

v0.470.0: New icons 0.470.0

Compare Source

New icons 🎨

• house-wifi (#​2723) by @​akshaymemane

Modified Icons 🔨

• rat (#​2692) by @​jguddas

v0.469.0: New icons 0.469.0

Compare Source

Modified Icons 🔨

• snowflake (#​2610) by @​karsa-mistmere
• sun-snow (#​2610) by @​karsa-mistmere
• thermometer-snowflake (#​2610) by @​karsa-mistmere

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @pangeacyber/[email protected]
npm error Found: [email protected]
npm error node_modules/react
npm error   react@"^19.0.0" from the root project
npm error   peer react@"^16.8 || ^17.0 || ^18.0 || ^19.0 || ^19.0.0-rc" from @radix-ui/[email protected]
npm error   node_modules/@radix-ui/react-context
npm error     @radix-ui/react-context@"1.1.1" from @radix-ui/[email protected]
npm error     node_modules/@radix-ui/react-toast
npm error       @radix-ui/react-toast@"^1.2.5" from the root project
npm error   9 more (@radix-ui/react-icons, ...)
npm error
npm error Could not resolve dependency:
npm error peer react@"^17.0.2 || ^18.2.0" from @pangeacyber/[email protected]
npm error node_modules/@pangeacyber/react-auth
npm error   @pangeacyber/react-auth@"^0.0.14" from the root project
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/react
npm error   peer react@"^17.0.2 || ^18.2.0" from @pangeacyber/[email protected]
npm error   node_modules/@pangeacyber/react-auth
npm error     @pangeacyber/react-auth@"^0.0.14" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2025-01-26T18_12_18_966Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2025-01-26T18_12_18_966Z-debug-0.log