lucide-react
A Lucide icon library package for React applications.
About
A Lucide icon library package for React applications.
What detecting lucide-react tells you about a site
lucide-react reveals the Lucide icon set as React components — the community fork of Feather icons that shadcn/ui adopted as its default. Finding it is another strong fingerprint of a shadcn/ui-style Tailwind app, and tells you icons are tree-shaken per-import rather than loaded as a sprite or font.
Why the exact lucide-react version matters
Lucide ships new icons continuously and occasionally renames them; the exact version tells you which icon set the build pinned and whether icon names in the code will resolve.
lucide-react in a real-world stack
When you find lucide-react in a bundle, it rarely travels alone. The shadcn/ui stack — tailwindcss, @radix-ui primitives, class-variance-authority — and React.
Quick facts
npm install lucide-reactCommon pairings
Packages this one expects to find in the same project. Each is also a Sourcemap Explorer detection target.
How Sourcemap Explorer detects lucide-react
lucide-react ships as v1.28.0, published 2026-07-30 and carries 0 direct dependencies, 1 peer dependency (react), 680 versions on the registry. Those exact numbers are the footprint Sourcemap Explorer matches when lucide-react rides inside a deployed bundle — here is how the detection works.
We catch lucide-react from two complementary signals: bundled source paths and the embedded package.json. Modern bundlers (webpack, Vite, esbuild, Rollup, Turbopack) preserve the original node_modules/lucide-react/ paths inside the JavaScript sourcemap's sources[] array — that's the canonical signal. When the matching package.json is also captured in sourcesContent[], we read the exact version field — patch number included. No regex guessing, no version inference.
- 1
Confirm the site exposes sourcemaps
In DevTools Network, check the response headers of any application script for `SourceMap` or `X-SourceMap`. Failing that, fetch the script's last 4 KB and look for a `//# sourceMappingURL=` comment — that map is where the `lucide-react` paths live.
- 2
Find the package in the bundle
Open DevTools → Network → reload. Click any application script and look at its sourcemap. Inside, search `sources[]` for entries matching `node_modules/lucide-react/` — every match confirms the package is bundled. The matching `sourcesContent[i]` for `node_modules/lucide-react/package.json` gives you the exact installed version.
- 3
Read the version directly from package.json
Run `jq -r '. as $m | $m.sources | to_entries[] | select(.value | endswith("node_modules/lucide-react/package.json")) | $m.sourcesContent[.key] | fromjson | .version' bundle.js.map`. Sourcemap Explorer automates the same query in the popup.
Major releases of lucide-react
When each major version first landed. Major bumps are where breaking changes live, so this timeline is the fastest way to date the lucide-react version a site actually ships against the ecosystem.
Recent versions
lucide-react README
Live mirror of the GitHub README, for reference. Updated whenever the repo's default branch changes.
Lucide icon library for React applications.
About · Icons · Documentation · License
Lucide React
Implementation of the Lucide icon library for React applications.
Installation
pnpm add lucide-react
npm install lucide-react
yarn add lucide-react
bun add lucide-react
Documentation
For full documentation, visit lucide.dev
Community
Join the Discord server to chat with the maintainers and other users.
License
Lucide is licensed under the ISC license. See LICENSE.
Sponsors
Hero backers 🦸
Awesome backers 🍺
Backers ☕
Other contributors 💸
You can find all our past and non-recurring financial contributors at our Open Collective page.
FAQ
What is lucide-react used for?
A Lucide icon library package for React applications.
How can I tell if a website is using lucide-react?
Open the page in Chrome with the Sourcemap Explorer extension installed and read the Stack tab. We catch `lucide-react` from two complementary signals: `node_modules/lucide-react/` paths inside the JavaScript sourcemap, and the embedded `package.json` we read for exact-version detection. Without the extension you can do the same lookup manually in DevTools — the steps are listed in the "How Sourcemap Explorer detects" section above.
How do I find out which version of lucide-react a website is running?
Read it straight from the site's JavaScript sourcemap. When a build ships source maps, the bundled `lucide-react/package.json` carries the exact `version` string — Sourcemap Explorer extracts it in one click on the Stack tab, and you can do it by hand in DevTools by opening the `.map` file and searching for `node_modules/lucide-react/package.json`. That is far more reliable than inferring the version from an asset-hash or a `?ver=` query string, which is all surface-level detectors have to go on. The current npm release is 1.28.0, but real deployments frequently run an older pinned version — which is exactly why reading the bundled number matters.
What is the latest version of lucide-react?
1.28.0, as published on the npm registry. The "Recent versions" table on this page lists the most recent 8 releases with their release dates. Sourcemap Explorer reports the version actually bundled into a site, which can lag the latest release by months on real-world deployments.
Is lucide-react actively maintained?
Very actively maintained — the last release shipped within the past three months. The last published release was 2026-07-30. Source code: https://github.com/lucide-icons/lucide.
Where can I read more?
Project homepage: https://lucide.dev. Source code: https://github.com/lucide-icons/lucide. Published on npm: https://www.npmjs.com/package/lucide-react. Licensed as ISC.
Keep reading on Sourcemap Explorer
Detection deep dives
Alternative tools
Detected by Sourcemap Explorer
When a bundle ships sourcemaps, we read the embedded package.json for lucide-react and report the precise version (the registry's latest is v1.28.0, published 2026-07-30; the bundled copy is often older). Without sourcemaps, an import / require in the page's scripts is enough to flag it.