storybook-eol / react-cdk Goto Github PK

It's better if we support code coverage support as well.

We can switch to Storybook v3!

Is there anyone interested in this?

Hello,

I was wondering what the status was of the react-cdk and if there's plans for continuing development of new features and bug fixes?
I only ask because my team and I have been working to put together a set of UI components for the company I work for, and we have concerns to tying our development/publishing process to a tool such as this that may not be maintained. In no way am I implying that your present/past efforts aren't appreciated, we just want know from the standpoint of ensuring we're using tools/technologies that will continue to receive support/updates.

Thanks for all your hard work!

. ./.scripts/prepublish.sh

is not recognized as an internal or external command (Windows 10)
npm-debug.pdf

I was noting some delay during "npm install" at this step.

node-pre-gyp install --fallback-to-build

It takes a while to move through this ES5 transpiring. Is this ok or some issue, please clarify ?

Hey @arunoda, great work! I was thinking, since many people may not know yeoman very well and may not feel comfortable using it. Maybe it would help to put yo react-cdk:update inside package.json as an NPM script, so people could simply type:

npm run update

Thoughts?

I use addWithInfo to show prop types of the component

import SmTextarea from '../index';
...
.addWithInfo('Prop Types', () => {
    return ( <Something /> );
}, { propTables: [SmTextarea] })

It works well while development but after deploying to GitHub it reduced to one letter (see here "t" Component)
Looks like it minified for publishing but is there any way to show real name of a component?

Running on osX / node v5.8.0.
Fresh from yo generation.
npm install runs OK, other scripts seem to be ok ok as well - including npm run prepublish
However running npm run storybook errors out with the following:

ERROR in ./src/stories/index.js
Module build failed: SyntaxError: /Users/Bart/Dev/Projects/Personal/react-comp-hello/src/stories/index.js: Unexpected token (7:4)
   5 | storiesOf('Button', module)
   6 |   .add('default view', () => (
>  7 |     <Button onClick={ action('button clicked') }>Hello</Button>
     |     ^

In my case, I've got the following directory structure:

  - myproject
    - webapp (meteor project)
    - npms
      - myuielement (created with react-cdk)

and the webapp/package.json is linking in the dependancies as follows:

    "myuielement": "../npms/myuielement",

This is working great... when running meteor locally.

But when I try to run meteor build it dies and gives me an error like the following:

$ meteor build /tmp/myproject-build

Unable to resolve some modules:

  "dist/index.js" in /Users/alan/Code/myproject/webapp/node_modules/myuielement/package.json (web.browser)

If you notice problems related to these missing modules, consider running:

  meteor npm install --save dist

I know it has to do with main: dist/index.js in package.json --- I experimented with removing the dist to no avail (didn't expect it to help, but I tried)

Do you have any recommendations for me? These packages are no use to anyone else, it seems silly to publish them. But I love the isolation of this pattern and would prefer to keep it if I can...

Ideas?

At first, thanks for this awesome tool ;)

When I try updating a react:cdk project via yo react-cdk:update I get an error like this:
$react-wizard: yo react-cdk:update

Error react-cdk:update 

You don't seem to have a generator with the name react-cdk:update installed.
You can see available generators with npm search yeoman-generator and then install them with npm install [name].
To see the 1 registered generators run yo with the `--help` option.

Regards,
Lukas

https://github.com/styled-components/styled-components

I was just following the README...
when I npm run storybook I got this error... Is there something wrong?

Module not found: Error: Cannot resolve module 'webpack-hot-middleware/client' in /Users/yixuan/project/react-data-growth

We need to see how it works other tools like Enzyme and so on.

For that, we need to move all the shell scripts to shelljs or similar.

Hi guys,
Thank you so much for this library. It has been very helpful for creating my component. I was wondering how I can go about creating a UMD build which i can host on a CDN.

Thanks again!

Hi,

I'm using React CDK for a collection of components, and I'd like to colocate the stories:

src
|-- components
|---|-- Button
|---|---|-- Button.js
|---|---|-- Button.test.js
|---|---|-- Button.stories.js
|---|-- Input
|---|---|-- Input.js
|---|---|-- Input.test.js
|---|---|-- Input.stories.js

In .storybook/config, I can simply update the loadStories function to do something like this:

const components = require.context('../src/components', true, /.stories.js$/);

function loadStories() {
  components.keys().forEach(filename => components(filename));
}

This works great, but there's a warning at the top of ./storybook/config:

// IMPORTANT
// ---------
// This is an auto generated file with React CDK.
// Do not modify this file.

I'm afraid that my changes will be overwritten, or at the very least, that there's a better way to do this. Please let me know :)

I can not understand, where to put files, which should be available, for example, by the link http://localhost:9001/images/ok-128.jpg

When i use sinopia and run npm install

user crisys11 is not allowed to access package @kadira/storybook

In publish_storybook.sh, I find the following code:
# run our compile script, discussed above
build-storybook -o .out

I think it references a script or capability provided elsewhere (maybe @kadira/storybook-deployer?), but I can't find it anywhere in this project. I'm attempting to implement this script cross platform (Windows), but I'm not sure where to go here.

Since storybookjs/storybook#473
is it possible to show favicon in deployed Storybook?

Build a simple project watcher, which look for React CDK updates. If when there's an new updates, it'll send an issue with the update.

Do you have advice for developing modules as stand-alone npm modules, but for use in a mantra (or Meteor imports dir structure) project?

I know I could symlink to src while developing and then change paths, but I think there's a way to tell the parent app to use a npm module at a specific path...?

If you have a development workflow you use for that sort of thing, I'd love to hear it.

thanks!
(as usual, you continue to make awesome stuff, thanks!)

I got the following error in Widnows 7

'.' is not recognized as an internal or external command,
operable program or batch file.

Then the install stops and application doesn't run. Please help

So, this allows to do cross browser testing and a lot of project uses use Karma.

See: https://github.com/semantic-release/semantic-release

This is great.