Storybook has built-in Typescript support, so your Typescript project should work with zero configuration needed.

Default configuration

The base Typescript configuration uses babel-loader for Typescript transpilation, and optionally fork-ts-checker-webpack-plugin for checking.

Each framework uses the base configuration unless otherwise specified:

  • Angular ignores the base and uses ts-loader and ngx-template-loader.
  • Vue ignores the base and uses ts-loader and applies it to both .tsx and .vue files.
  • React adds react-docgen-typescript-plugin to the base.

Main.js configuration

To make it easier to configure Typescript handling, use the typescript field in your .storybook/main.js.

The following code snippets shows the fields for you to use with TypeScript:

checkAllOptionally run fork-ts-checker-webpack-pluginboolean
checkOptionsAllOptions to pass to fork-ts-checker-webpack-plugin if it's enabledSee Docs
reactDocgenReactWhich react docgen processor to run: "react-docgen-typescript", "react-docgen", falsestring or false
reactDocgenTypescriptOptionsReactOptions to pass to react-docgen-typescript-plugin if react-docgen-typescript is enabled.See docs

Overriding the configuration to infer additional props

The configuration provided above will remove any props from any third party libraries.

If it's required you can adjust the configuration and include the extra props.

Adjust the configuration as shown below and any third party props will be displayed as soon as you restart your Storybook.

Next time you restart your Storybook the extra props will also be in the UI.

If you run into an issue where the extra props aren't included, check how your component is being exported. If it's using a default export, change it to a named export and the extra props will be included as well.