EGOIST
EGOIST
For example to test against node 4/5/7, it copies the project and creates 3 folder to run each version, before running it executes `git clean -xfd` to remove unwanted files...
Currently we're using `readme` property to display detailed usage, I'm thinking about deprecating that and using `.styleguide` method for adding styleguide to each component instead. ```js play('Button', module) .styleguide(markdownCode) .add('with...
since we manage to use `example` to show example code, and `readme` to show some intro for the component you wanna play, I think a play-loader may suit the needs....
It should be easy to add vue-play to a [webpack-template](https://github.com/vuejs-templates/webpack) project. Maybe send a PR to https://github.com/vuejs-templates/webpack/tree/master/docs to introduce how.
https://github.com/webpack/webpack/issues/4039 - webpack 2 According to this, we use `module.exports` [here](https://github.com/vue-play/vue-play/blob/master/src/play.js#L42) and if you use `import` in `./play/preview.js` the `module.exports` will be undefined and read-only...
for example, `left panel closed` => `?leftClosed=1` what we want to keep: - panel state - tab state, which is active - search filter
Make a console component that you can use to debug your component without open chrome devtools. Like the ones in react-storybook and vue-devtools
- fix `for` attribute, adding `id` attribute to `input` elements - use native `required` attribute
like github issues' comment reaction. 