@fluentui/react-icons

IMPORTANT PLEASE READ @fluentui/react-icons has been major bumped to 2.x. There are some key changes in the api and usages. The main ones are:

The general icons are now resizeable using styling(i.e. scaling using the height and width props or using fontSize prop, etc). Ex: <AccessTimeFilled fontSize={40}>
There is now a more general icon offering included with the sized icons. Instead of importing <AccessTime24Filled>, you just import <AccessTimeFilled>.
The sized icons are still available, and are recommended if you know the specific size you want your icons to be. For the general case, the more general icons are available to you.

(Note: For those who were consuming @fluentui/react-icons v 0.x, we are releasing a new set of icons under @fluentui/react-icons v 1.x. You can still use 0.x version for the old icons, but if you major bump to 1.x, you will be using the new icons. The Fabric MDL2 SVG Icon set that is released with v 0.x has been rereleased in @fluentui/react-icons-mdl2.)

Fluent System Icons are a collection of familiar, friendly, and modern icons from Microsoft.

User story

@fluentui/react-icons are SVG based icons wrapped in a React element. Because each icon is its own element, you only need to import what you need for your application.

There are two different states of each icon, Filled and Regular, so you can choose what works best for your application. These are by default sized to 1em, and can be scaled up or down to suit your developer needs.

There are also helpful interfaces that will allow you to add styling to fit the icons to your specific application.

Usage

In order to use these icons, simply import them as import { [Componentname][state] } from @fluentui/react-icons as follows:

import { AccessTimeFilled } from "@fluentui/react-icons";

The previous icon offerings are scalable, but if you know what size you want to use for your icons, and you are not planning on using multiple sizes, it is recommended to use the sized icons. These are the same icons as the general case, but in multiple different sizes, built to look pixel perfect at those specific sizes. You can import the sized icons in a similar way:

import { AccessTime24Filled } from "@fluentui/react-icons";

You can also style the icons using the FluentIconsProps interface, with the className prop or the primaryFill prop.

Finally, you can bundle the Filled and Regular versions of each icon into a compound icon component using the bundleIcon method. The bundleIcon() function returns a component with both states of the icon, and you can then use the classnames iconFilledClassName and iconRegularClassName to style this compound component.

If you would like to get the bundled icon without any of the default styling, then add the filled prop to the new component and the icon will not have any default styling. To style this new icon, add a user defined stylesheet to the icon component.

import * as React from "react";
import * as ReactDOM from "react-dom";

import {
    AccessTimeFilled,
    AccessTimeRegular,
    bundleIcon,
    iconFilledClassName,
    iconRegularClassName
} from "@fluentui/react-icons";
import { makeStyles } from "@griffel/react";


const iconStyleProps: FluentIconsProps = {
    primaryFill: "purple",
    className: "iconClass"
};

const useIconStyles = makeStyles({
    icon: {
        ":hover": {
            [`& .${iconFilledClassName}`]: {
                display: "none"
            },
            [`& .${iconRegularClassName}`]: {
                display: "inline"
            }
        }
    }
})

const AccessTime = bundleIcon(AccessTimeFilled, AccessTimeRegular)
const rootElement = document.getElementById("root");
const styles = useIconStyles();
ReactDOM.render(
    <div className={styles.icon}>
        <AccessTime aria-label="AccessTime" {...iconStyleProps} />
    </div>,
    rootElement
    )

Using the icon font

If, for performance or other reasons, you wish to use the font implementation of these icons rather than the SVG implementation, you can specify "fluentIconFont" as a condition for the import, either via Node >= 12.19.0 or webpack >= 5.0.0.

// webpack.config.js
module.exports = {
  //...
  resolve: {
    conditionNames: ['fluentIconFont', 'require', 'node'],
  },
};

If you do choose this route, you may wish to use @fluentui/react-icons-font-subsetting-webpack-plugin to optimize the font assets.

API Contract

[!IMPORTANT] This library does not strictly follow semantic versioning. Breaking changes may occur in patch releases.

Versioning Strategy

Due to the monorepo architecture, all packages share a unified release cycle. Both minor (feature additions) and patch (bug fixes and icon updates) changes are released as PATCH version bumps only. This means:

2.0.X → 2.0.Y may include new features, icon additions, or breaking changes
Major version bumps (2.X.X → 3.0.0) are reserved for significant API redesigns

Breaking Changes

While we strive to maintain API stability, there are two scenarios where breaking changes can occur outside of major version updates:

Icon Removal: Icons may be removed from the library due to legal or licensing issues. When an icon asset is removed, any code importing that icon will break.
Icon Renaming: Icons may be renamed to better reflect their purpose or to align with design system updates. This will break existing imports that reference the old icon name.

These are the only two types of breaking changes that deviate from standard semantic versioning practices. All other aspects of our API contract follow semantic versioning conventions - meaning additions, bug fixes, and internal improvements will not break your existing code.

💡 NOTE: We could remedy these breaking change scenarios by providing empty icon placeholders, but we believe a failing build pipeline is preferable to silently shipping invalid UI with blank icons to your users.

Recommendation: When upgrading, even for patch versions, review the release notes for any removed or renamed icons to ensure your application isn't affected.

Atomic API

The Atomic API provides a more granular way to import icons, with each icon variant exported individually from dedicated module files. This approach can significantly improve tree-shaking and reduce bundle sizes, especially when you only use a small subset of the available icons.

Benefits

Better tree-shaking: Import only the exact icon variants you need
Smaller bundles: Each icon variant is in its own file, allowing bundlers to eliminate unused code more effectively
Grouped variants: Related icon variants (different sizes and styles) are grouped together in a single file for convenience

File Organization

Icons with multiple variants are automatically grouped into a single file:

Example: access-time.js contains all AccessTime variants (AccessTime20Regular, AccessTime24Filled, etc.)
Average: ~9 exports per file (mix of sizes and styles)

This grouping strikes a balance between granularity and convenience, making it easy to import related variants while still maintaining excellent tree-shaking characteristics.

Using API directly

Icons are available via two export maps:

@fluentui/react-icons/svg/* - SVG-based icons
@fluentui/react-icons/fonts/* - Font-based icons

// Import individual icon variants from grouped files
import { AccessTime20Filled, AccessTime24Filled, AccessTime20Regular } from "@fluentui/react-icons/svg/access-time";
import { Add16Filled, Add20Filled } from "@fluentui/react-icons/fonts/add";

function MyComponent() {
  return (
    <>
      <AccessTime20Filled />
      <Add16Filled />
    </>
  );
}

TypeScript Configuration

IMPORTANT: TypeScript users must use moduleResolution: "bundler" (or "node16"/"nodenext") in their tsconfig.json to properly resolve these atomic exports:

{
  "compilerOptions": {
    "moduleResolution": "bundler"
  }
}

Without this setting, TypeScript will not be able to resolve the individual icon exports from the grouped files.

Using API via build transform

Migrating a larger codebase to the new performant atomic imports might be a daunting task. To make this migration more straightforward, you can leverage build-time import transforms to get all the benefits without modifying your actual code.

These transforms automatically rewrite imports from:

import { AccessTime24Filled } from "@fluentui/react-icons";

To the optimized atomic import:

import { AccessTime24Filled } from "@fluentui/react-icons/svg/access-time";

This transformation happens at build time, so your source code remains unchanged while your bundled output gets the full tree-shaking benefits.

Babel

If you use Babel for transpilation, add babel-plugin-transform-imports with the following setup:

// @filename .babelrc.js
module.exports = {
  presets: [
    // ... your preset configuration
  ],
  plugins: [
    [
      'transform-imports',
      {
        '@fluentui/react-icons': {
          transform: (importName) => {
            const withoutSuffix = importName.replace(
              /(\d*)?(Regular|Filled|Light|Color)$/,
              ''
            );

            const kebabCase = withoutSuffix
              .replace(/([a-z0-9])([A-Z])/g, '$1-$2')
              .toLowerCase();

            return `@fluentui/react-icons/svg/${kebabCase}`;
          },
          preventFullImport: false,
          skipDefaultConversion: true,
        },
      },
    ],
  ],
};

SWC

If you use SWC for transpilation, add @swc/plugin-transform-imports with the following setup:

// @filename .swcrc
{
  "jsc": {
    "experimental": {
      "plugins": [
        [
          "@swc/plugin-transform-imports",
          {
            "@fluentui/react-icons": {
              "transform": [
                [
                  "(\\D*)(\\d*)?(Regular|Filled|Light|Color)",
                  "@fluentui/react-icons/svg/{{ kebabCase memberMatches.[1] }}"
                ]
              ],
              "preventFullImport": false,
              "skipDefaultConversion": true,
              "handleDefaultImport": false,
              "handleNamespaceImport": false
            }
          }
        ]
      ]
    }
  }
}

Viewing the icons in a webpage

You can view the full list of available icons by type: regular or filled

Appendix and FAQ

:::info Find this document incomplete? Leave a comment! :::

包详细信息