How to extend an archetype.

[trusktr]

Alright, I think I've got the hang of it. I'm wondering how to extend an archetype. Suppose I'm using an archetype, but I'd like to add a loader that the archetype's webpack config doesn't have. Any recommendation on extending the Webpack config? Any recommendation on how to extend an archetype in general?

[trusktr]

More specifically, I'm wondering: suppose I have archetype-a with it's webpack config (or babel, or gulp, or any config and procedures). I'd like to make a slight modification to it, but rather making an archetype-b package by copying archetype-a, I'm wondering how I might make an extension of archetype-a and publish only that minimal extension as archetype-b so that most of the configurations and procedures are contained in archetype-a with only the minimal change in archetype-b.

[trusktr]

For Webpack cases, Mozilla Neutrino has an interesting API for sharing and modifying webpack configs. There's also webpack-merge. These might help to some degree (for Webpack stuff only). Now, just gotta figure out how to (or if we already can?) "extend" archetypes so that we don't have to copy over all the package.json:scripts, etc.