Skip to content

chore(deps): update dependency lucide-react to ^0.474.0#24

Merged
Azathothas merged 1 commit intomainfrom
renovate/lucide-react-0.x
Jan 25, 2025
Merged

chore(deps): update dependency lucide-react to ^0.474.0#24
Azathothas merged 1 commit intomainfrom
renovate/lucide-react-0.x

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented Jan 10, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
lucide-react (source) ^0.469.0 -> ^0.474.0 age adoption passing confidence

Release Notes

lucide-icons/lucide (lucide-react)

v0.474.0: New icons 0.474.0

Compare Source

Modified Icons 🔨

v0.473.0: New icons 0.473.0

Compare Source

Modified Icons 🔨

v0.472.0: New icons 0.472.0

New icons 🎨

What's Changed

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

v0.471.1: Hotfix Lucide React exports

Compare Source

What's Changed

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 🎨

v0.470.0: New icons 0.470.0

Compare Source

New icons 🎨
Modified Icons 🔨

Configuration

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

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, 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 renovate Bot force-pushed the renovate/lucide-react-0.x branch from 467d1ad to ac7c664 Compare January 17, 2025 12:13
@renovate renovate Bot changed the title chore(deps): update dependency lucide-react to ^0.471.0 chore(deps): update dependency lucide-react to ^0.472.0 Jan 17, 2025
@renovate renovate Bot force-pushed the renovate/lucide-react-0.x branch from ac7c664 to aea9b8d Compare January 19, 2025 08:12
@renovate renovate Bot changed the title chore(deps): update dependency lucide-react to ^0.472.0 chore(deps): update dependency lucide-react to ^0.473.0 Jan 19, 2025
@renovate renovate Bot force-pushed the renovate/lucide-react-0.x branch from aea9b8d to 5aae7e9 Compare January 23, 2025 17:02
@renovate renovate Bot changed the title chore(deps): update dependency lucide-react to ^0.473.0 chore(deps): update dependency lucide-react to ^0.474.0 Jan 23, 2025
@Azathothas Azathothas merged commit f0f2c4c into main Jan 25, 2025
@renovate renovate Bot deleted the renovate/lucide-react-0.x branch January 25, 2025 06:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant