Ryan Roemer

We spent a *lot* of time wrangling with all of the different things that `npm` tree flattening can do with having separated prod and dev archetypes -- prod archetypes having...

@d-asensio -- thanks for chiming in and providing a detailed write up of your thoughts! ## Aside -- real npm lifecycle commands. Your archetype should never include real npm lifecycle...

`LOCAL_DEV` isn't meant to be used as a normal thing. Symlinks are going to be problematic for many things with builder. Your best bet is to probably look into https://github.com/FormidableLabs/lank#readme...

@exogen -- I'd be open to a PR for #20 if you wanted to try it. We have very good test coverage, so should be able to make sure nothing's...

@exogen -- Can you think of a way _without_ having us do Bash-style `resolve`? Because that significantly increases the complexity of an otherwise simple tool? I.e., how does `builder` do...

Also, the other issue we'll have to tackle in _any_ scenario: What happens when `ROOT/webpack.config.js` and archetype diverge?

Thinking about this more, here's I think what's rubbing me about making `builder` a much more sophisticated tool. Right now: - `builder run WHATEVER` is a drop-in replacement for `npm...

> I think we should just go with the simple & strict design for the initial release – it's forwards-compatible with this feature being considered in the future anyway. Yep....

@chaseadamsio @exogen -- Pairing together your ideas and discussions offline, for a strawman of: ``` yaml --- overrides: "builder-react-component/config/webpack/webpack.config.js": "webpack.config.js" ``` In all of the `builder-react-component` that have a: ```...

@boygirl @chaseadamsio -- Here's my background of thinking: Next up is a `builder-react-app` archetype for `converter-react`. The frontend test, lint stuff will be virtually identical to `builder-react-component`. So, hence "should...