Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
wants to merge 1 commit into
base: dependency-update
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 20, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
lucide-react (source) ^0.468.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 🔨

v0.469.0: New icons 0.469.0

Compare Source

Modified Icons 🔨


Configuration

📅 Schedule: Branch creation - "after 6am and before 6pm" (UTC), 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.

Copy link

vercel bot commented Dec 20, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
lapelle-v2 ❌ Failed (Inspect) Jan 23, 2025 4:31pm

@renovate renovate bot changed the title fix(deps): update dependency lucide-react to ^0.469.0 fix(deps): update dependency lucide-react to ^0.471.0 Jan 10, 2025
@renovate renovate bot force-pushed the renovate/lucide-monorepo branch from cdf6166 to be66e90 Compare January 10, 2025 14:32
@renovate renovate bot force-pushed the renovate/lucide-monorepo branch from be66e90 to 0de75be Compare January 19, 2025 08:16
@renovate renovate bot changed the title fix(deps): update dependency lucide-react to ^0.471.0 fix(deps): update dependency lucide-react to ^0.473.0 Jan 19, 2025
@renovate renovate bot changed the title fix(deps): update dependency lucide-react to ^0.473.0 fix(deps): update dependency lucide-react to ^0.474.0 Jan 23, 2025
@renovate renovate bot force-pushed the renovate/lucide-monorepo branch from 0de75be to 56e63ef Compare January 23, 2025 16:31
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.

0 participants