包详细信息

react-docgen-typescript-webpack-plugin

strothj48.4kMIT1.1.0

Webpack plugin to generate docgen information from Typescript React components.

storybook, react, docgen, typescript

自述文件

react-docgen-typescript-webpack-plugin

Webpack plugin to generate docgen information from Typescript React components.

Installation

Add the package as a development dependency.

$ npm install --save-dev react-docgen-typescript-webpack-plugin

or

$ yarn add --dev react-docgen-typescript-webpack-plugin

Add the plugin to your Webpack configuration.

const path = require("path");
const genDefaultConfig = require("@storybook/react/dist/server/config/defaults/webpack.config.js");
const TSDocgenPlugin = require("react-docgen-typescript-webpack-plugin");

module.exports = (baseConfig, env) => {
  const config = genDefaultConfig(baseConfig);

  config.module.rules.push({
    test: /\.tsx?$/,
    include: path.resolve(__dirname, "../src"),
    loader: require.resolve("ts-loader"),
  });

  config.plugins.push(new TSDocgenPlugin());

  config.resolve.extensions.push(".ts", ".tsx");

  return config;
};

Usage

Storybook Info Plugin

Include the withInfo decorator as normal.

Special Note:

The Storybook Info addon will only attempt to read Docgen information when the story name matches the name of the component. So if you have a component named ColorButton, then you will have to use something like:

storiesOf("...", module).add("ColorButton", ...)


import * as React from "react";
import { storiesOf } from "@storybook/react";
import { withInfo } from "@storybook/addon-info";
import ColorButton from "./ColorButton";

storiesOf("Components", module).add(
  "ColorButton",
  withInfo({ inline: true })(() => (
    <ColorButton color="blue">Color Button</ColorButton>
  )),
);

Experimental

This plugin is mostly a hack job at the moment. It is a work in progress so it is most likely not suitable for production. Pull requests are most welcome.

Limitations

This plugin makes use of the great project: https://github.com/styleguidist/react-docgen-typescript

It is subject to the same limitations. Component docgen information can not be generated for components who are only exported as default. You can work around the issue by exporting the component using a named export.

CURRENT LIMITATION The current implementation seems to have trouble with the compiler option module being set to esnext.

import * as React from "react";

interface ColorButtonProps {
  /** Buttons background color */
  color: "blue" | "green";
}

/** A button with a configurable background color. */
export const ColorButton: React.SFC<ColorButtonProps> = props => (
  <button
    style={{
      padding: 40,
      color: "#eee",
      backgroundColor: props.color,
      fontSize: "2rem",
    }}
  >
    {props.children}
  </button>
);

export default ColorButton;

Contributing

Pull requests are welcome. For major changes, please open an issue first to discuss what you would like to change.

Please make sure to update tests as appropriate.

License

MIT

更新日志

Changelog

[3.7.2] - 2020-03-29

[3.7.1] - 2020-03-09

Fixed

[3.6.0] - 2019-11-24

Added

Thanks @patricklafrance: https://github.com/strothj/react-docgen-typescript-loader/pull/73

[3.5.0] - 2019-11-20

Added

Thanks @folz: https://github.com/strothj/react-docgen-typescript-loader/pull/72

  • Expose the componentNameResolver parser option. This allows override the name resolution for components.

[3.4.0] - 2019-11-15

Added

Thanks @patricklafrance: https://github.com/strothj/react-docgen-typescript-loader/pull/69

  • Make the name of the type property attached to generated docs configurable.

[3.3.0] - 2019-09-30

Added

Thanks @evless: https://github.com/strothj/react-docgen-typescript-loader/pull/64

  • Default values can be displayed as something other than just string types.

[3.2.1] - 2019-09-17

Changed

[3.2.0] - 2019-09-01

Added

Thanks @nekitk: https://github.com/strothj/react-docgen-typescript-loader/pull/59

  • Default values for stateless components can now be generated from props destructuring.
  • Passing new parser option (shouldExtractLiteralValuesFromEnum) which allows to parse TypeScript enums and string unions to docgen enum of their values: If false (like before): type: { name: "\"blue\" | \"green\"" } or type: { name: "ColorEnum" } If true: type: { name: "enum", value: [ { value: "\"blue\"" }, { value: "\"green\""} ] }

[3.1.1] - 2019-08-09

Fix

[3.1.0] - 2019-04-02

[3.0.1] - 2019-01-20

  • Republish to resolve potential file permissions issue due to publishing from Windows. Closes #35.

[3.0.0] - 2018-09-20

Changed

  • Bump react-docgen-typescript dependency to v1.9.0
  • Removed the loader options includes and excludes. Closes #15
  • Use the loader-utils Webpack page to process loader options. Closes 22.

[2.2.0] - 2018-08-11

Added

[2.1.1] - 2018-06-13

Changed

  • Bump react-docgen-typescript dependency to v1.6.0:

    parse can be called with multiple source file paths (thanks to @marionebl PR #91)
    upgraded typescript version and fixed parsing comment problem (thanks to @kbukum PR #97)

[2.1.0] - 2018-05-27

Changed

  • Bump react-docgen-typescript dependency to v1.5.0:

    Remove spread logic.
    Support spread default props.
    Use folder name if file name is index.
    chore(parser): refactor displayName extraction
    chore(Parser): read displayName
    parse tsconfig.json mirroring TSC’s process
    Added support for referenced default props in stateless components
    support referenced defaultProps
    Extracts default props from stateless components

[2.0.3] - 2018-03-26

Fixed

[2.0.2] - 2018-03-03

Fixed

  • Use original source text when generating amended code (resolves #7).