Right now the happy path is that we configure everything for you: Babel, Webpack, ESLint, etc. With shadowing, if the user provides a .babelrc (or whatever cosmiconfig can read for any given project) then we use their config instead of our own. This will allow users to config what they want and leave ours for whatever they don't want to config.
For v2, let's aim to make configurable:
ESLint
TSLint
Babel
Flow
TypeScript
And let's punt of Webpack. I'm not convinced we can make Webpack configurable in a useful right now without writing a complicated layer on top.
ESLint won't work due to limitations with how ESLint resolves plugins. .babelrc went out with v0.5.0. Flow and TS will go out when they're implemented.
Basic idea of shadowing (term subject to change):
Right now the happy path is that we configure everything for you: Babel, Webpack, ESLint, etc. With shadowing, if the user provides a .babelrc (or whatever cosmiconfig can read for any given project) then we use their config instead of our own. This will allow users to config what they want and leave ours for whatever they don't want to config.
For v2, let's aim to make configurable:
And let's punt of Webpack. I'm not convinced we can make Webpack configurable in a useful right now without writing a complicated layer on top.