The hardest part about Builder is making an Archetype. about builder HOT 4 CLOSED

I see why builder is powerful, but the how is not as clear as I'd like. After trying to run things, it starts to become more clear when seeing the output and errors. Also, just moving stuff around and reconfiguring an existing project can be daunting, and a couple typos, etc, was throwing me off too. If I end up realizing how docs can be better I'll make PRs...

from builder.

I mean, I know maybe not all Archetypes will be the same, but for example, most of them will probably want to have builder-support, and a -dev version, etc. Lot's of things that can be generated as a starting point.

from builder.

Is there an Archetype for generating Archetypes with builder-init?

Well, I suppose I can make a meta archetype for making builder archetypes. Perhaps figuring a way to make archetypes extensible would be more useful. It'd probably depend on the archetype that is being extended (f.e. which tools it uses, webpack, babel, etc). In the final case, it might make sense to make an archetype for generating and managing archetypes that extend a single type of parent archetype.

My goal would be to be able to make an extending archetype that might tweak some config or add a webpack loader for a specific file type not covered by the parent archetype, etc.

from builder.

Closing, I think I thought my way through towards a path leading to a possible action that might yield a solution.

from builder.