I tried to follow the initial steps from here: https://www.learnstorybook.com/intro-to-storybook/react/en/get-started/

running:

npx create-react-app taskbox
cd taskbox

Then when I ran:
npx -p @storybook/cli sb init

I get the error TypeError: Cannot set property 'storybook' of undefined

This is the full message in my terminal:

 sb init - the simplest way to add a

@diegohaz - i noticed a couple of minor spelling errors on the main site:

Basic stack
It includes everything necessary to build a tipical web app with focus on productivity and developer experience.
Learn more about the recomended workflow

Should be typical, and recommended.

Just an FYI.

Thanks!

add defaultValue and value props support for some form like components so that we can control the components switch between controlled and uncontrolled. it was used by some popular UI library like Material UI and antd. I have written a tiny module ([rc-value](https://github.com/beizh

https://github.com/leandrowd/react-responsive-carousel/blob/efcf86acdffc9ef929aff524eb17da8dd0890a36/src/components/Carousel.js#L94

With React 16.9 the lifecycle function "componentWillReceiveProps" is marked as deprecated will be even removed in React 17.

As you can read here https://fb.me/react-async-component-lifecycle-hooks

But there is a new lifecycle function

  static getDeriv

Description

This is probably related to #190. From https://github.com/storybookjs/storybook/blob/master/MIGRATION.md#deprecate-displayname-parameter:

In 5.3, the CSF loader decouples the story's name/id, which means that displayName is no longer necessary. Unfortunately, this is a breaking change for any code that uses the story name field. Storyshots relies on story name, and the appropriate migration i

https://github.com/storybookjs/storybook-deployer/blob/6ee1d3e00596979257ef89bc05aede9ecf0f45aa/bin/storybook_to_ghpages#L70

Would be nice to add an option for adding additional git push flags. In our case, something like --no-verify would be crucial.

Seems now we don't need this addon because most of the feature provided by stroybook-readme are implemented at storybook

https://medium.com/storybookjs/storybook-docspage-e185bc3622bf

The docs are currently written for someone familiar with jest mocha and Enzyme.

1. Perhaps add at the beginning:

Specs is an addon to Storybook.
Storybook allows the developer during development to visually see a component or part of it, and interactively see immediate changes to the code. It also helps document the project with visual examples.
Specs adds the ability to

In README.md it says by adding for example "test": "jest" ignite will generate tests, which should be "tests":"jest" (with s) according to for example this line in the saga generat

AddOn: v1.4.0 
Node: v8.14.0
React:16.2.0
Storybook/react: 3.4.0

yarn screenshot
yarn run v1.12.3
$ storybook-chrome-screenshot -p 9001 --debug 
 DEBUG  [CLI Options] { port: '9001',
  host: 'localhost',
  staticDir: undefined,
  configDir: '.storybook',
  outputDir: '__screenshots__',
  filterKind: undefined,
  filterStory: undefined,
  browserTimeout: 30000,
  par

Got this reply in an /r/react thread:

Nice. I kept looking and looking where you generate the different manifest.json files. But it looks like you used a combined one.

Be aware that there are slight differences in FF and Chrome supported extensions. So I had to keep separate manifest.json files for each browser.

The problem is that each of the browsers doesn't load the extension if

To pass stories via the command line, the --stories argument needs to be parsed. It is simply merged into the config as a string here: https://github.com/chrisvxd/story2sketch/blob/master/src/server/index.js#L61

For it to work I had to add:

  if (newConfig.stories && newConfig.stories !== 'all') {
    newConfig.stories = JSON.parse(newConfig.stories);
  }

to tidyConfig().

T

When using apolloStorybookDecorator, I get an error from apollo client that "You must specify link & cache properties on the config object". Not sure what I can do to resolve this.

Feature request

While not ideal visually, we've still done our best to support IE11.

We haven't had a single visitor using the Internet Explorer Browser in 3 months according to Google Analytics. Since it's so unpopular, we can stop supporting it entirely. That requires changing the .browserslistrc.

Aside from this change, this issue can serve as weak PSA that we are also allowed to

The new gutter props that were added via #191 need to be documented.

It also should be detailed how shift works and how it adds a gutter.

• build a page with govuk-react on codesandbox with a Page, H1, H2, DateField, Button (and more if you want)
• build the same page with govuk-frontend on another codesandbox
• do a pixel perfect comparison, e.g. using a Chrome extension or Photoshop
• if there are any differences, figur

Current status (Update: Nov 14)

Docs-Mode is now available in Storybook v5.2.0!
If you want well-integrated, SB native looks, and easy to use documentation, please try it!
(documentation for events and slots are available from v5.3.0)

• [Storybook Docs: Technical Preview(Guide docs)](https://docs.google.com/document/d/1u

Reproducible sample code

`yarn add v1.17.3
[1/4] 🔍 Resolving packages...
warning jest > jest-cli > jest-config > jest-environment-jsdom > jsdom > left-pad@1.3.0: use String.prototype.padStart()
error An unexpected error occurred: "https://registry.npmjs.org/react-native-template-react-native-template-typescript: Not found".
info If you think this is a bug, please open a bug report with t