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

[Snyk] Upgrade lucide-react from 0.469.0 to 0.473.0 #51

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

RectiFlex
Copy link
Owner

@RectiFlex RectiFlex commented Feb 8, 2025

snyk-top-banner

Snyk has created this PR to upgrade lucide-react from 0.469.0 to 0.473.0.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 6 versions ahead of your current version.

  • The recommended version was released 22 days ago.

Release notes
Package name: lucide-react
  • 0.473.0 - 2025-01-17

    Modified Icons 🔨

  • 0.472.0 - 2025-01-17

    New icons 🎨

    What's Changed

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

    Full Changelog: 0.471.1...0.472.0

  • 0.471.2 - 2025-01-17
  • 0.471.1 - 2025-01-13

    What's Changed

  • 0.471.0 - 2025-01-10

    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 🎨

  • 0.470.0 - 2025-01-10

    New icons 🎨

    Modified Icons 🔨

  • 0.469.0 - 2024-12-20

    Modified Icons 🔨

from lucide-react GitHub release notes

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

Summary by Sourcery

Enhancements:

  • Upgrade lucide-react to 0.473.0.

Snyk has created this PR to upgrade lucide-react from 0.469.0 to 0.473.0.

See this package in npm:
lucide-react

See this project in Snyk:
https://app.snyk.io/org/jace.lander/project/bdf39633-ceed-4c2e-b6f6-79dd1fa2448f?utm_source=github&utm_medium=referral&page=upgrade-pr
Copy link

vercel bot commented Feb 8, 2025

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

Name Status Preview Comments Updated (UTC)
aicf ✅ Ready (Inspect) Visit Preview 💬 Add feedback Feb 8, 2025 5:38am

Copy link

stackblitz bot commented Feb 8, 2025

Review PR in StackBlitz Codeflow Run & review this pull request in StackBlitz Codeflow.

Copy link

sourcery-ai bot commented Feb 8, 2025

Reviewer's Guide by Sourcery

This PR upgrades the lucide-react dependency from 0.469.0 to 0.473.0. The update is implemented by modifying the version specified in package.json and propagating the changes to package-lock.json, ensuring dependency safety and new feature inclusion based on Snyk's recommendations.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change Details Files
Updated the lucide-react dependency version
  • Changed the lucide-react version in package.json from 0.469.0 to 0.473.0
  • Propagated the version update in package-lock.json to maintain consistency
package.json
package-lock.json

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!
  • Generate a plan of action for an issue: Comment @sourcery-ai plan on
    an issue to generate a plan of action for it.

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

Copy link

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We have skipped reviewing this pull request. It seems to have been created by a bot ('[Snyk]' found in title). We assume it knows what it's doing!

Copy link

codeautopilot bot commented Feb 8, 2025

PR Summary

This pull request upgrades the lucide-react package from version 0.469.0 to 0.473.0. The update includes several enhancements and fixes:

  • New Icons: The update introduces new icons such as battery-plus, map-plus, and triangle-dashed.
  • Modified Icons: Some existing icons, like package and rat, have been modified.
  • Dynamic Icon Component: A new DynamicIcon component has been introduced, which allows for dynamic icon rendering based on icon names. This is particularly useful for applications that need to display icons dynamically, such as those using content management systems.
  • Bug Fixes: Fixes related to alias imports and type module declarations in package.json have been implemented.
  • Potential Breaking Changes: The package now uses the "exports" property in package.json, which might affect projects that directly import scripts from the package.

Overall, this update is beneficial for keeping dependencies current, which helps in maintaining security and compatibility with other packages.

Review Checklist

  • Ensure the updated package version does not introduce breaking changes to the existing codebase.
  • Verify that the new features and fixes are compatible with the current project requirements.
  • Test the application to ensure that the new icons and dynamic icon component work as expected.

Suggestion

If your project does not require dynamic icon rendering, it is advisable to continue using static icon components to avoid increased build times and additional network requests. However, if dynamic rendering is needed, consider testing the DynamicIcon component thoroughly to ensure it integrates well with your existing setup.

This comment was generated by AI. Information provided may be incorrect.

Current plan usage: 13%

Have feedback or need help?
Documentation
support@codeautopilot.com

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.

2 participants