Skip to content

Conversation

eric-schneider
Copy link
Contributor

@eric-schneider eric-schneider commented Jul 16, 2025

This PR updates to the latest version of lucide-static (0.525.0) and @fontsource/material-icons-outlined (5.2.6).

This comment was marked as outdated.

@plpesvc-ds

This comment was marked as outdated.

@eric-schneider
Copy link
Contributor Author

@colegoldsmith as part of updating the package, I nuked my package-lock.json file and node_modules folder and did a fresh npm install (running node v22.17.1 and npm 10.9.2).

This resulted in a big change to package-lock.json and reported the following deperecation warnings. I'm not sure how big of a deal this is.

npm warn deprecated [email protected]: This package is deprecated. Use https://socket.dev/npm/package/eta instead.
npm warn deprecated [email protected]: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm warn deprecated [email protected]: Modern JS already guarantees Array#sort() is a stable sort, so this library is deprecated. See the compatibility table on MDN: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/sort#browser_compatibility
npm warn deprecated [email protected]: See https://github.com/lydell/source-map-url#deprecated
npm warn deprecated [email protected]: Rimraf versions prior to v4 are no longer supported
npm warn deprecated @humanwhocodes/[email protected]: Use @eslint/config-array instead
npm warn deprecated [email protected]: Please see https://github.com/lydell/urix#deprecated
npm warn deprecated [email protected]: Rimraf versions prior to v4 are no longer supported
npm warn deprecated [email protected]: https://github.com/lydell/resolve-url#deprecated
npm warn deprecated [email protected]: Glob versions prior to v9 are no longer supported
npm warn deprecated @humanwhocodes/[email protected]: Use @eslint/object-schema instead
npm warn deprecated [email protected]: See https://github.com/lydell/source-map-resolve#deprecated
npm warn deprecated [email protected]: You or someone you depend on is using Q, the JavaScript Promise library that gave JavaScript developers strong feelings about promises. They can almost certainly migrate to the native JavaScript promise now. Thank you literally everyone for joining me in this bet against the odds. Be excellent to each other.
npm warn deprecated
npm warn deprecated (For a CapTP with native promises, see @endo/eventual-send and @endo/captp)
npm warn deprecated [email protected]: Please use @jridgewell/sourcemap-codec instead
npm warn deprecated [email protected]: Upgrade to fsevents v2 to mitigate potential security issues
npm warn deprecated [email protected]: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm warn deprecated [email protected]: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
npm warn deprecated [email protected]: This SVGO version is no longer supported. Upgrade to v2.x.x.
npm warn deprecated [email protected]: Version no longer supported. Upgrade to @latest
npm warn deprecated [email protected]: This version is no longer supported. Please see https://eslint.org/version-support for other options.
npm warn deprecated [email protected]: This version is no longer supported. Please see https://eslint.org/version-support for other options.

77 vulnerabilities (2 low, 42 moderate, 33 high)

@colegoldsmith
Copy link
Collaborator

@eric-schneider I fear there might be some repercussions with creating a new package lock using a newer version of node and npm. Unless we intend to start using a newer version of node/npm best practice is to not delete the package.lock.json and update any packages with the currently used version of node. There is a .nvmrc file that shows what node version this repo uses (16.20.2). Nvm is a good tool for this, lets you switch node version on the fly with nvm use

This comment was marked as outdated.

@plpesvc-ds

This comment was marked as outdated.

Copy link
Contributor

github-actions bot commented Jul 17, 2025

UI bundle preview build successful! ✅
Deploying bundle preview.
Deploy successful! View preview

@plpesvc-ds
Copy link

plpesvc-ds commented Jul 17, 2025

Build successful! ✅
Deploying draft.
Deploy successful! View draft

@eric-schneider eric-schneider changed the title Upgrade lucide-static package Update Lucide and Material icon packages Jul 17, 2025
@eric-schneider eric-schneider self-assigned this Jul 17, 2025
@eric-schneider eric-schneider merged commit 370bcc4 into main Jul 17, 2025
2 checks passed
@eric-schneider eric-schneider deleted the bump-lucide branch July 17, 2025 21:52
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.

3 participants