ExtReact Docs Help


The documentation for the ExtReact product diverges somewhat from the documentation of other Sencha products. The sections below describe documentation for all products except where indicated as unique to ExtReact.

Terms, Icons, and Labels

Many classes have shortcut names used when creating (instantiating) a class with a configuration object. The shortcut name is referred to as an alias (or xtype if the class extends Ext.Component). The alias/xtype is listed next to the class name of applicable classes for quick reference.

ExtReact component classes list the configurable name prominently at the top of the API class doc followed by the fully-qualified class name.

Access Levels

Framework classes or their members may be specified as private or protected. Else, the class / member is public. Public, protected, and private are access descriptors used to convey how and when the class or class member should be used.

Member Types

Member Syntax

Below is an example class member that we can disect to show the syntax of a class member (the lookupComponent method as viewed from the Ext.button.Button class in this case).

lookupComponent ( item ) : Ext.Component

Called when a raw config object is added to this container either during initialization of the items config, or when new items are added), or {@link #insert inserted.

This method converts the passed object into an instanced child component.

This may be overridden in subclasses when special processing needs to be applied to child creation.


item :  Object

The config object being added.


The component to be added.

Let's look at each part of the member row:

Member Flags

The API documentation uses a number of flags to further commnicate the class member's function and intent. The label may be represented by a text label, an abbreviation, or an icon.

Class Icons

- Indicates a framework class

- A singleton framework class. *See the singleton flag for more information

- A component-type framework class (any class within the Ext JS framework that extends Ext.Component)

- Indicates that the class, member, or guide is new in the currently viewed version

Member Icons

- Indicates a class member of type config

Or in the case of an ExtReact component class this indicates a member of type prop

- Indicates a class member of type property

- Indicates a class member of type method

- Indicates a class member of type event

- Indicates a class member of type theme variable

- Indicates a class member of type theme mixin

- Indicates that the class, member, or guide is new in the currently viewed version

Class Member Quick-Nav Menu

Just below the class name on an API doc page is a row of buttons corresponding to the types of members owned by the current class. Each button shows a count of members by type (this count is updated as filters are applied). Clicking the button will navigate you to that member section. Hovering over the member-type button will reveal a popup menu of all members of that type for quick navigation.

Getter and Setter Methods

Getting and setter methods that correlate to a class config option will show up in the methods section as well as in the configs section of both the API doc and the member-type menus just beneath the config they work with. The getter and setter method documentation will be found in the config row for easy reference.

ExtReact component classes do not hoist the getter / setter methods into the prop. All methods will be described in the Methods section

History Bar

Your page history is kept in localstorage and displayed (using the available real estate) just below the top title bar. By default, the only search results shown are the pages matching the product / version you're currently viewing. You can expand what is displayed by clicking on the button on the right-hand side of the history bar and choosing the "All" radio option. This will show all recent pages in the history bar for all products / versions.

Within the history config menu you will also see a listing of your recent page visits. The results are filtered by the "Current Product / Version" and "All" radio options. Clicking on the button will clear the history bar as well as the history kept in local storage.

If "All" is selected in the history config menu the checkbox option for "Show product details in the history bar" will be enabled. When checked, the product/version for each historic page will show alongside the page name in the history bar. Hovering the cursor over the page names in the history bar will also show the product/version as a tooltip.

Search and Filters

Both API docs and guides can be searched for using the search field at the top of the page.

On API doc pages there is also a filter input field that filters the member rows using the filter string. In addition to filtering by string you can filter the class members by access level, inheritance, and read only. This is done using the checkboxes at the top of the page.

The checkbox at the bottom of the API class navigation tree filters the class list to include or exclude private classes.

Clicking on an empty search field will show your last 10 searches for quick navigation.

API Doc Class Metadata

Each API doc page (with the exception of Javascript primitives pages) has a menu view of metadata relating to that class. This metadata view will have one or more of the following:

Expanding and Collapsing Examples and Class Members

Runnable examples (Fiddles) are expanded on a page by default. You can collapse and expand example code blocks individually using the arrow on the top-left of the code block. You can also toggle the collapse state of all examples using the toggle button on the top-right of the page. The toggle-all state will be remembered between page loads.

Class members are collapsed on a page by default. You can expand and collapse members using the arrow icon on the left of the member row or globally using the expand / collapse all toggle button top-right.

Desktop -vs- Mobile View

Viewing the docs on narrower screens or browsers will result in a view optimized for a smaller form factor. The primary differences between the desktop and "mobile" view are:

Viewing the Class Source

The class source can be viewed by clicking on the class name at the top of an API doc page. The source for class members can be viewed by clicking on the "view source" link on the right-hand side of the member row.

ExtReact 6.5.3


Configuring Webpack and Babel

Sencha recommends using Webpack 2+ to build your ExtReact application. ExtReact includes a webpack plugin that bundles and optimizes the ExtReact components used in your application. This guide documents the configuration options for that plugin.


First, install the ExtReact webpack plugins from Sencha's NPM registry:

npm install --save-dev @extjs/reactor-webpack-plugin

Then, import it into your webpack configuration:

const ExtReactWebpackPlugin = require('@extjs/reactor-webpack-plugin');

module.exports = {
    plugins: [
        new ExtReactWebpackPlugin({
            // config options

Webpack Plugin Configuration

ExtReactWebpackPlugin's constructor accepts a configuration object with several settings.

Common Options


default: false

Set to true when creating a production build to compress and optimize the ExtReact bundle. Defaults to false.


default: "theme-material"

The name of one of the built-in ExtReact themes:

  • theme-material
  • theme-ios
  • theme-triton
  • theme-neptune

You can also specify the name of a custom theme located in ext-react/packages or the path to a custom theme. For example, to use a custom theme located at ext-react/packages/custom-theme:

new ExtReactWebpackPlugin({
    theme: 'custom-theme'


An array of directories containing Ext JS overrides to include in the bundle. For example:

new ExtReactWebpackPlugin({
    overrides: ['./ext-react/overrides']


default: "ext-react"

The path to the directory where bundle should be written relative the build directory.

Less Common Options


An array of names of Ext JS packages to include in the bundle. This option is only needed when using @extjs/reactor with Ext JS. It is not needed when using ExtReact. For example:

new ExtReactWebpackPlugin({
    packages: ['charts', 'd3']


If third-party packages are used, an array of directories where they are located. The name of each third-party package should also be included in the packages config. This option is only needed when using @extjs/reactor with Ext JS. It is not needed when using ExtReact.

new ExtReactWebpackPlugin({
    packageDirs: ['./ext-packages']


The path to your local copy of the Ext JS SDK. This option is only needed when using @extjs/reactor with Ext JS. It is not needed when using ExtReact.


default: /.jsx?$/

The regular expression used to determine which files are scanned for usage of ExtReact components


default: "modern"

The toolkit to use: "modern" or "classic". The classic toolkit can only be used with a local copy of the Ext JS SDK. When using classic you'll need to configure the sdk and packages options as well. This option is only needed when using @extjs/reactor with Ext JS. It is not needed when using ExtReact.

new ExtReactWebpackPlugin({
    toolkit: 'classic'


default: true

Set to false to disable tree shaking in development builds. This makes incremental rebuilds faster by including all ExtReact components in the initial build and thus not requiring a rebuild after each change. This option only takes affect when production is set to false.

Configuring the Webpack Plugin Using .ext-reactrc

All of the settings documented above can also be placed in a json file located in the root of your project named .ext-reactrc. If present, the settings in .ext-reactrc are merged with those passed to ExtReactWebpackPlugin's constructor. Where there are conflicts, values in .ext-reactrc take precedent. Sencha Themer uses .ext-reactrc when you apply a theme to your application.

Here is an example .ext-reactrc file:

    "theme": "my-custom-theme"

Configuring Babel

In order to build your application, @extjs/reactor-babel-plugin must be included in your babel configuration and ES6 module transpilation must be turned off. Here is an example .babelrc:

  "presets": [
    [ "es2015", { "modules": false } ],
  "plugins": [

Configuring TypeScript

Apps that use TypeScript should also use @extjs/reactor-babel-plugin. In your webpack config, add babel-loader to your rule for ts|tsx files:

    test: /\.(ts|tsx)$/,
    exclude: /node_modules/,
    use: [
            loader: 'babel-loader',
            options: {
                "plugins": [
            loader: 'awesome-typescript-loader'

Then, in your tsconfig.json, set the "module" config to "es2015". Here is an example tsconfig.json from the ExtReact TypeScript Boilerplate:

  "compilerOptions": {
    "sourceMap": true,
    "target": "es5",
    "jsx": "react",
    "module": "es2015",
    "moduleResolution": "node",
    "emitDecoratorMetadata": true,
    "experimentalDecorators": true,
    "declaration": false,
    "noImplicitAny": false,
    "noImplicitReturns": false,
    "removeComments": true,
    "strictNullChecks": false,
    "outDir": "build",
    "lib": [
  "exclude": [

ExtReact 6.5.3