Using Office UI Fabric Core and Fabric React in SPFx client-side web parts

Important: You must upgrade existing projects to use @microsoft/sp-build-web@1.0.1 or later in order to use the Office UI Fabric React components. See the instructions at the end of this article for additional information.

The Office UI Fabric is the official front-end framework for building experiences in Office 365 and SharePoint. SharePoint provides seamless integration with Fabric that enables Microsoft to deliver a robust and consistent design language across various SharePoint experiences such as modern team sites, modern pages, and modern lists. Additionally, the Office UI Fabric is available for developers in the SharePoint Framework when building custom SharePoint solutions.

Integration and usage of the Office UI Fabric is still a work in progress. The purpose of this document is to provide a status update to SPFx developers. Very soon we will publish a final plan.


There are two parts of the Office UI Fabric that are available to be used by developers:

  1. Office UI Fabric Core a.k.a. Fabric Core - this is a set of core styles, typography, a responsive grid, animations, icons, and other fundamental building blocks of the overall design language.

  2. Office UI Fabric React a.k.a. Fabric React - this package contains a set of React components built on top of the Fabric design language.

Some of the goals of the SharePoint Framework are to allow both Microsoft and customers to build rich, beautiful, and consistent solutions on top of SharePoint. In accordance with these goals, here are our design principles:

  • All customers should be able to smoothly and reliably consume Fabric Core and Fabric React in their solutions.
  • Microsoft will roll out updated experiences that consume updated versions of Fabric Core and Fabric React in SharePoint without conflicting with customer's solutions.
  • Customers can customize and override the styles, designs, and components to tailor to their solution's needs.
  • Customers should be able to build solutions with non-React based frameworks.


Microsoft uses Fabric Core and Fabric React in SharePoint. Microsoft regularly pushes updates to SharePoint Online and SharePoint experiences are likely to continue updating the version of Fabric Core and Fabric React used. These updates could potentially conflict with third party solutions built with previous versions of Fabric Core and Fabric React, which could cause exceptions in those customizations. The primary reason for these types of breaks is the use of Global CSS styles in both Fabric libraries. Such conflicts need to be avoided at all costs.

In order to achieve reliability, one of the main problems we need to solve is that of Global CSS styles. Currently, both Fabric Core and fabric.component.css use global styles.

For these reasons, currently, customer solutions cannot yet safely use portions of the Office UI Fabric. However, we understand that developers need Fabric Core and Fabric React to build their solutions. We are working to resolve this as quickly as possible.

Here's a summary of currently supported options for using the Office UI Fabric within SharePoint Framework solutions based on the JavaScript framework selected:

  • React - You can only use the Office UI Fabric safely by statically linking to the Fabric React components
  • Other JS libraries - Usage of the Office UI Fabric within a SharePoint Framework solution is not supported

An example of the current versioning challenge: A web part consumes the class ms-Icon--List when they build their web part. At a later date, Fabric decides to change the definition of this class. The web part that had made an assumption regarding the previous implementation can break. Similarly, let's say, the web part uses the class ms-Button from Fabric React. Then the Fabric React team later changes the implementation of the Button in a big way along with the styles in the ms-Button class. That would likely break the web part.

The challenge with Global CSS styles is well explained in the following presentation within the context of React and JS: React CSS in JS.

How to use the Office UI Fabric React in a Safe Way in Your Solution

Here are the recommendations for using Fabric in React based web parts in a safe and reliable way:

  • Web part developers should place an explicit dependency on the specific version of Fabric React version 2.0 in their package.json file "office-ui-fabric-react":"2.34.2". Please note, Fabric React versions older than 2.x are not supported.
  • Web part developers need to statically link to the Fabric React components. This includes the Fabric React component in your web part bundle. This will ensure that if the page level implementation of the Button were to change, it will not affect your web part adversely.
  • Overriding Fabric React component styles should be done only sparingly and within a local scope. A developer can override using custom CSS classes with !important and style tags. Both will have higher specificity than the component classes. Please note, if you override using a simple class, then you may run into load order issues. i.e. If ms-Button loads after your class, it will take precedence because their specificity is the same.
  • Theming should just work as is. No extra work is required on the part of the developer.

The following code snippet shows how to perform static and dynamic linking of libraries:

  // This sample demonstrates how static linking should be done for Fabric React components.
  // Remember to explicitly add a dependency on a specific version of 
  // office-ui-fabric-react in your package.json file.

  // correct - static linking.
  import { Button } from 'office-ui-fabric-react/lib/Button';

  // incorrect - dynamic linking.
  import { Button } from '@microsoft/office-ui-fabric-react';

  render() {
      <Button>click me</Button>

Understanding this approach and its shortcomings:

  • Components in your web part are locked to the version of Fabric React you used when you built the web part. They will not automatically evolve with the surrounding page. You will need to manually update your web part to adapt to newer versions of Fabric React.
  • The page may be less performant as it may load more CSS, but it will be reliable.
  • Static linking bloats up your web part bundle, but dynamic linking is too fragile considering future updates to be introduced in SharePoint Online. Static linking is the only approach that is officially supported when Office UI Fabric React is being used in SharePoint Framework solutions.

Currently unsupported features

  • Office UI Fabric Core: The Fabric Core implementation currently uses global styles e.g. .ms-Icon--List and hence there is no safe way to use Fabric core in your web part without potential challenges in the future. Work is being done to address this challenge and more details will be shared when the situation changes.

  • fabric.components.css: This file contains global classes that conflict with Fabric React. e.g. .ms-Button in fabric.component.css will override the Button styles in a Fabric React Button component. Including fabric.component.css in a web part is bound to break the surrounding page or other web parts on the page. We are working on a solution and will release an update shortly.

Using the Office UI Fabric with Non-React Based Web Parts

Using the Office UI Fabric with non-React based web parts is currently not supported and implementations could experience unexpected issues when newer versions of the Office UI Fabric are released. We are working on creating a reliable integration story for Office UI Fabric Core, fabric.component.css, and Non-React based web parts.

Additional Details on the CSS Challenge with Office UI Fabric

The following concepts and references provide insights on the challenge with Office UI Fabric usage in the context of client-side web parts.

Global CSS styles and how to avoid them at all cost: this is a big problem. Today, both Fabric Core and Fabric React have global styles. Lack of any native solutions from the browser to manage the style scoping makes this a very difficult problem.

  • Scope CSS is in early stages of discussion.
  • iframes are not a good option to isolate styles.
  • Web Components is another standard that talks about scoped styles but is still in discussion stages.

    This discussion explains the problem well. There is plenty of other documentation on the web about the solutions to the global namespace menace.

CSS Specificity and how it applies to web UI. Higher specificity styles override the lower specificity styles, but the key thing to understand is how the specificity rules apply. In general, the precedence order from highest to lowest is as follows:

  • The style attribute (e.g. style="background:red;")
  • Id selectors (e.g. #myDiv { })
  • Class selectors (e.g. .myCssClass{}), attributre selectors (e.g. [type="radio"]), and pseudo-classes (e.g. :hover)
  • Type selectors (e.g. h1)

Loading order - If two classes are applied on an element and they have the same specificity, the class that is loaded later takes precedence. As shown in the code below, the button will appear red. If the order of the style tags is changed, the button will appear green. This is an important concept, and if not used correctly, the user experience can become load order dependent (i.e. inconsistent).

  .greenButton { color: green; }
  .redButton { color: red; }
  <button class="greenButton redButton"></button>

Other Approaches Considered and Discarded

Here are some additional insights on the other approaches which were considered, but discarded, since they did not achieve the key objectives to enable 3rd party developers to safely use the Office UI Fabric styles.

Office UI Fabric Core

The web part developer would not be required to do anything explicitly to get the scoping to work. We planned to solve this problem through CSS specificity and descendant selectors. The Fabric Core team would ship multiple copies of Fabric Core css. e.g. fabric-6.css, fabric-6-scoped.css, fabric-6.0.0.css, fabric-6.0.0-scoped.css.

All the styles in the scoped CSS files would be inside a descendant selector e.g. "ms-Fabric-core--v6 ms-Icon--List". At compile time, the tooling would collect the version of the Office UI Fabric Core the web part was built with. This version could be the one that comes with SPFx. Alternatively, web part developers could specify an explicit dependency on a specific version of Office UI Fabric Core in their package.json file.

The web part div would be assigned this scope i.e. <div data-sp-webpart class="ms-Fabric-core--v6">. The framework would load the specific major version of the Fabric core scoped CSS file. If the web part was built with version 6.0.0 of Fabric core CSS, the framework would download fabric-6-scoped.css when the web part was loaded.

The rest of the page would contain unscoped Office UI Fabric Core styles. This way, as per CSS specificity rules, the scoped CSS would take precedence within the web part div. The web part and its contents would align to the specific version of the Office UI Fabric Core the developer had chosen.

Overriding Fabric Core styles would not be supported.

// Sample of how the scoping would work.
import { SPComponentLoader } from '@microsoft/sp-loader';

export default class MyWebPart {
    constructor() {


protected render(): void {
  <div className={css('ms-Fabric-core--v6')}>
    { // Rest of the web part UI }

After analyzing this strategy for a while it was decided that the descendant selector approach has two serious shortcomings that would make it impossible to build a web part that would never break.

Lack of reliable nesting support - This approach only works if the Microsoft user experience (i.e. page and first party web parts) use an unscoped version of the Office UI Fabric Core. i.e. ms-Icon--List while the third party web parts only use scoped Office UI Fabric Core css as explained above. The reason being that the specificity of the scoped CSS applied on the web part overrides unscoped CSS on the page. Keep in mind, as explained above, if CSS specificity of two classes is the same, then their loading order plays a role in how the CSS classes will be applied. The class that loads later will take precedence. Hence, the higher specificity of the scoped CSS is important in getting a consistent experience.

Further, multiple extensions, one contained in the other, cannot use different Fabric Core versions. For instance, in the following example, only ms-Fabric-core--v6 would get applied:

<div className={css('ms-Fabric-core--v6')}>
  { // Rest of the web part UI }
    { // inside of this SPExtension trying to use different Fabric core version does not work }
    <div className={css('ms-Fabric-core--v8')}>

Here's a more simplistic sample demonstrating the challenge:

  <title>CSS specifity test</title>
  .myButton {
      background-color: brown;
      color: brown;
      height: 20px;
      width: 40px;
  .scope2 .myButton {
      background-color: green;
      color: green;
  .scope3 .myButton {
      background-color: yellow;
      color: yellow;
  .scope1 .myButton {
      background-color: red;
      color: red;
    <span>These tests demonstrate descendant selectors, nesting and load order problems.</span>

      <span>This test depicts that a descendant selector with the same specificity does not allow nesting.
      All buttons below do not take the innermost scope (i.e. they should be different colors), but they are all red.
      Further, if you change the ordering of the style tags, the colors will change. (i.e. the UI is load order dependant.)</span> 
      <div class='scope1'>
        <button class='myButton'</button>
        <div class='scope2'>
          <button class='myButton'></button>
          <div class='scope3'>
            <button class='myButton'></button>

Leakage from unscoped classes - There is another problem with descendant selectors. Note in the above example, the height and the width styles from the unscoped myButton class are applied to all the buttons. This implies that a change in that style could inadvertently break html using scoped markup. Say for example, for some reason at the app level we decide to make height 0px on the myButton class. That will result in all 3rd party web parts using the myButton class to have a height of 0px (i.e. a serious regression in the user experience).

Updating an existing project

In your project's package.json, update the @microsoft/sp-build-web dependency to at least version 1.0.1, delete your project's node_modules directory, and run npm install.