storybook-eol / getstorybook Goto Github PK

Currently we use some unicode chars in this repo.
So, it won't properly in windows (older) boxes.

Therefore, we need to detect that and use some polyfill or get rid of using those chars.
We may could use this to detect the unicode support.

Related issue: storybookjs/storybook#550

Detect webpack based projects and try to reuse the existing webpack config if possible. Or if not, ask the user to edit accordingly.

CRA might add it or make something separate for it, but in the meantime, an idea for storybook

facebook/create-react-app#418

issue:

The package still has a significant number of downloads.
currently, this version of the package installs Storybook v2
we want to stimulate users to switch to the Storybook v3

what can we do:

• publish @storybook/cli to getstorybook package on npm as a temporary solution
• deprecate it completely when the number of downloads will drop enough

Since get-storybook hides the config folder when building a create-react-app project, is there another way to include custom tags in the head of the iframe?

Replacing the index file for storybook is not a good thing. So, we need to come up with a better way to add storybook to any RN project.

storybook-eol/react-native-storybook#51 is a good candidate.

I'm currently stuck on this:

I think there should be feedback so the user knows npm isn't just stuck.
Especially given that npm 3 gives you an overall sense of progression.

CRAP supports a public directory from v0.5 as described here. We should add this to the list of static directories by default.

Node 4 is the stable version so many people use that. It comes with npm 2 so tree isn't flat.
This is the output I get:

npm run storybook

> [email protected] storybook /Users/gaearon/p/test
> start-storybook -p 9009


React Storybook started on => http://localhost:9009/

webpack built 8075a01bcca1d6c58491 in 56ms
Hash: 8075a01bcca1d6c58491
Version: webpack 1.13.1
Time: 56ms
                   Asset     Size  Chunks             Chunk Names
static/preview.bundle.js  22.7 kB       0  [emitted]  preview
static/manager.bundle.js  22.4 kB       1  [emitted]  manager
chunk    {0} static/preview.bundle.js (preview) 64 bytes [rendered]
    [0] multi preview 64 bytes {0} [built] [4 errors]
chunk    {1} static/manager.bundle.js (manager) 40 bytes [rendered]
    [0] multi manager 40 bytes {1} [built] [2 errors]

ERROR in multi preview
Module not found: Error: Cannot resolve module 'webpack-hot-middleware/client' in /Users/gaearon/p/test
 @ multi preview

ERROR in multi preview
Module not found: Error: Cannot resolve module 'babel' in /Users/gaearon/p/test
 @ multi preview

ERROR in multi manager
Module not found: Error: Cannot resolve module 'babel' in /Users/gaearon/p/test
 @ multi manager

ERROR in multi preview
Module not found: Error: Cannot resolve module 'babel' in /Users/gaearon/p/test
 @ multi preview

ERROR in multi preview
Module not found: Error: Cannot resolve module 'babel' in /Users/gaearon/p/test
 @ multi preview

ERROR in multi manager
Module not found: Error: Cannot resolve module 'babel' in /Users/gaearon/p/test
 @ multi manager

We had to put a bunch of require.resolves in Create React App to work around this.

Add some getting started stories for setup it quickly.

Detect Meteor projects and add essential configs.

Whenever I try getstorybook on a fresh Meteor project with react and react-dom :

 • Installing dependencies. ✖

     An error occurred while installing dependencies.

No npm-debug.log on the root of my project nor in the location where global storybook is installed.

I don't have any proxy. Slow start works but I hope getstorybook gonna require all the Meteor css.

PS : I also npm i