Add support for Storybook

[peterp]

Storybook allows you to develop your components in isolation, away from all the conflated cruft of your real app.

"Props in, views out! Make it simple to reason about."

• Add a yarn storybook command
• This will search for files with *.stories.js, *.stories.tsx, and *.stories.jsx
• Load Redwood's webpack configuration
• Load the user's webpack configuration.
• Load Providers

Generators

• Add story file to generated Cell components. Closes Storybook support for cells #231
• Add story file to generated component.
• Add story file to generated pages.
• Add story file to generated layouts.

Configuration options for users

• How would a user overwrite the Providers?
• How would the user add addons?

Debug

• LiveReload doesn't appear to be working.

[peterp]

@RobertBroersma I'm going to be using your GraphQL msw mocking abilities over here :)

[tmeasday]

Hi @peterp, let us know if need any help or advice! PS I recently created this document with some thoughts about how we are thinking about data mocking in Storybook (we want to add a docs page on it soon), and would be interested you are thinking about it at your end.

[peterp]

Ooooh @tmeasday Thanks for this! We started using Mock Service Worker for our tests, and it's pretty amazing for mocking GraphQL, rest and HTTP requests.

It's great because it's client agnostic and has a very minimal API design! I should be done with this PR soon and I would love to show you the approach, maybe we can jump on a call early next week?

[jtoar]

@peterp I'll take a look at this this weekend and start writing some docs!

[peterp]

@jtoar Awesome! Hit me up if you have any questions!

[tmeasday]

Let's do it @peterp -- I'll send you an email

[toxsick]

Hey Guys,

are there any tracking issues for "How would a user overwrite the Providers?" or "How would the user add addons" ?

[peterp]

@toxsick I've added an issue over here: #1595