formidable-react-component-boilerplate
formidable-react-component-boilerplate copied to clipboard
FormidableLabs
I see that this is made with a yeoman generator, not a builder-init template. Any reason to use a yo generator instead of a builder template?
Some discussion has happened around this already, but the gist is that we have `builder` and `builder-react-component` in `dependencies`. And most of our current repos, which are pre-Builder, have `babel`...
TODO when FormidableLabs/builder-react-component#4 is resolved.
webpack hot server doesn't shutdown gracefully causing EADDRINUSE errors
- [ ] Hook up Coveralls account - [ ] Add to Travis YML - [ ] Track that coverage is generated by - [x] Client - [ ] Server...
Problem: Already lose stack traces because part of a test bundle. Will get worse with coverage enabled. Possible solutions: - https://github.com/novocaine/sourcemapped-stacktrace (Remap error stacks manually).
w/ Rowdy + WebdriverIO - [ ] Decide on automation ID strategy. - [ ] Coverage. - [ ] Travis CI.