react-icons
SVG React icons of popular icon packs using ES6 imports
About
SVG React icons of popular icon packs using ES6 imports
What detecting react-icons tells you about a site
react-icons bundles dozens of icon sets (Font Awesome, Material, Feather, Bootstrap and more) behind a single import surface, so finding it says the team wanted icon variety without committing to one design language. It's a pragmatic, ship-fast choice rather than a bespoke SVG system, and it often hints at a smaller team or an MVP where visual consistency took a back seat to breadth. Because each icon is a tree-shakeable component, its mere presence does not imply bloat, but a sloppy import of a whole set in the bundle is a tell-tale sign of a build that was never audited for size.
Why the exact react-icons version matters
react-icons tracks upstream icon libraries, so the version pins which generation of those sets shipped and which import paths existed. Older majors predate proper tree-shaking via per-set entrypoints, meaning a dated version on a heavy page can quietly drag in far more than the icons actually rendered. The version also dates the project against React's own era.
react-icons in a real-world stack
When you find react-icons in a bundle, it rarely travels alone. Almost always alongside React and a component library like Chakra, Mantine or a Tailwind setup.
Quick facts
npm install react-iconsCommon pairings
Packages this one expects to find in the same project. Each is also a Sourcemap Explorer detection target.
How Sourcemap Explorer detects react-icons
react-icons ships as v5.7.0, published 2026-06-30 and carries 0 direct dependencies, 1 peer dependency (react), 86 versions on the registry. Those exact numbers are the footprint Sourcemap Explorer matches when react-icons rides inside a deployed bundle — here is how the detection works.
We catch react-icons from two complementary signals: bundled source paths and the embedded package.json. Modern bundlers (webpack, Vite, esbuild, Rollup, Turbopack) preserve the original node_modules/react-icons/ 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 `react-icons` 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/react-icons/` — every match confirms the package is bundled. The matching `sourcesContent[i]` for `node_modules/react-icons/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/react-icons/package.json")) | $m.sourcesContent[.key] | fromjson | .version' bundle.js.map`. Sourcemap Explorer automates the same query in the popup.
Major releases of react-icons
When each major version first landed. Major bumps are where breaking changes live, so this timeline is the fastest way to date the react-icons version a site actually ships against the ecosystem.
Recent versions
react-icons README
Live mirror of the GitHub README, for reference. Updated whenever the repo's default branch changes.
React Icons
Include popular icons in your React projects easily with react-icons, which utilizes ES6 imports that allows you to include only the icons that your project is using.
Installation (for standard modern project)
yarn add react-icons
# or
npm install react-icons --save
example usage
import { FaBeer } from "react-icons/fa";
function Question() {
return (
<h3>
Lets go for a <FaBeer />?
</h3>
);
}
View the documentation for further usage examples and how to use icons from other packages. NOTE: each Icon package has it's own subfolder under react-icons you import from.
For example, to use an icon from Material Design, your import would be: import { ICON_NAME } from 'react-icons/md';
Installation (for meteorjs, gatsbyjs, etc)
Note This option has not had a new release for some time. More info https://github.com/react-icons/react-icons/issues/593
If your project grows in size, this option is available. This method has the trade-off that it takes a long time to install the package.
yarn add @react-icons/all-files
# or
npm install @react-icons/all-files --save
example usage
import { FaBeer } from "@react-icons/all-files/fa/FaBeer";
function Question() {
return (
<h3>
Lets go for a <FaBeer />?
</h3>
);
}
Icons
You can add more icons by submitting pull requests or creating issues.
Configuration
You can configure react-icons props using React Context API.
Requires React 16.3 or higher.
import { IconContext } from "react-icons";
<IconContext.Provider value={{ color: "blue", className: "global-class-name" }}>
<div>
<FaFolder />
</div>
</IconContext.Provider>;
| Key | Default | Notes |
|---|---|---|
color | undefined (inherit) | |
size | 1em | |
className | undefined | |
style | undefined | Can overwrite size and color |
attr | undefined | Overwritten by other attributes |
title | undefined | Icon description for accessibility |
Migrating from version 2 -> 3
Change import style
Import path has changed. You need to rewrite from the old style.
// OLD IMPORT STYLE
import FaBeer from "react-icons/lib/fa/beer";
function Question() {
return (
<h3>
Lets go for a <FaBeer />?
</h3>
);
}
// NEW IMPORT STYLE
import { FaBeer } from "react-icons/fa";
function Question() {
return (
<h3>
Lets go for a <FaBeer />?
</h3>
);
}
Ending up with a large JS bundle? Check out this issue.
Adjustment CSS
From version 3, vertical-align: middle is not automatically given. Please use IconContext to specify className or specify an inline style.
Global Inline Styling
<IconContext.Provider value={{ style: { verticalAlign: 'middle' } }}>
Global className Styling
Component
<IconContext.Provider value={{ className: 'react-icons' }}>
CSS
.react-icons {
vertical-align: middle;
}
TypeScript native support
Dependencies on @types/react-icons can be deleted.
Yarn
yarn remove @types/react-icons
NPM
npm remove @types/react-icons
Contributing
./build-script.sh will build the whole project. See also CI scripts for more information.
Development
yarn
cd packages/react-icons
yarn fetch # fetch icon sources
yarn build
Add/Update icon set
First, check the discussion to see if anyone would like to add an icon set.
https://github.com/react-icons/react-icons/discussions/categories/new-icon-set
The SVG files to be fetched are managed in this file. Edit this file and run yarn fetch && yarn check && yarn build.
https://github.com/react-icons/react-icons/blob/master/packages/react-icons/src/icons/index.ts
Preview
Note The project is not actively accepting PR for the preview site at this time.
The preview site is the react-icons website, built in Astro+React.
cd packages/react-icons
yarn fetch
yarn build
cd ../preview-astro
yarn start
Demo
The demo is a Create React App boilerplate with react-icons added as a dependency for easy testing.
cd packages/react-icons
yarn fetch
yarn build
cd ../demo
yarn start
Why React SVG components instead of fonts?
SVG is supported by all major browsers. With react-icons, you can serve only the needed icons instead of one big font file to the users, helping you to recognize which icons are used in your project.
Related Projects
Licence
MIT
- Icons are taken from the other projects so please check each project licences accordingly.
FAQ
What is react-icons used for?
SVG React icons of popular icon packs using ES6 imports
How can I tell if a website is using react-icons?
Open the page in Chrome with the Sourcemap Explorer extension installed and read the Stack tab. We catch `react-icons` from two complementary signals: `node_modules/react-icons/` 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 react-icons a website is running?
Read it straight from the site's JavaScript sourcemap. When a build ships source maps, the bundled `react-icons/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/react-icons/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 5.7.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 react-icons?
5.7.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 react-icons actively maintained?
Very actively maintained — the last release shipped within the past three months. The last published release was 2026-06-30. Source code: https://github.com/react-icons/react-icons.
Where can I read more?
Project homepage: https://github.com/react-icons/react-icons#readme. Source code: https://github.com/react-icons/react-icons. Published on npm: https://www.npmjs.com/package/react-icons. Licensed as MIT.
Detected by Sourcemap Explorer
When a bundle ships sourcemaps, we read the embedded package.json for react-icons and report the precise version (the registry's latest is v5.7.0, published 2026-06-30; the bundled copy is often older). Without sourcemaps, an import / require in the page's scripts is enough to flag it.