JSPM

@storybook/cli

5.0.6
  • ESM via JSPM
  • ES Module Entrypoint
  • Export Map
  • Keywords
  • License
  • Repository URL
  • TypeScript Types
  • README
  • Created
  • Published
  • Downloads 2011479
  • Score
    100M100P100Q228456F
  • License MIT

Storybook's CLI - easiest method of adding storybook to your projects

Package Exports

  • @storybook/cli/bin/index

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (@storybook/cli) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

Storybook CLI

Storybook CLI (Command Line Interface) is the easiest way to add Storybook to your project.

In the future it will also add other useful generators and migration tooling.

Screenshot

Just go to your project and run:

cd my-app
npx -p @storybook/cli sb init

That's all you've to do.


Yarn support

The CLI supports yarn. If you have installed yarn in your system, it'll detect it and use yarn instead of npm.

If you don't want to use yarn always you can use the --use-npm option like this:

npx -p @storybook/cli sb init --use-npm

Flow support

It also supports flow files. By default, jscodeshift, the tool used to transform the source files, uses babel to read the files. To be able to transform any flow annotated file, you need to use the flow parser.

npx -p @storybook/cli sb init --parser flow

For more information visit: storybook.js.org


Manually specify project type

If the CLI cannot detect your project type, it will ask you. You can also force it to use a particular project type:

npx -p @storybook/cli sb init --type <type>

Where type is one of the project types defined in project_types.js