How should you structure a generator to be composable and reusable?

• A. Break functionality into subgenerators and compose with them; expose options to control behavior
• B. Put all logic in a single monolithic generator
• C. Hard-code templates to avoid complexity
• D. Avoid exposing options to simplify usage

Answer: (A)

Modular design and composition are the keys to reusable Yeoman generators. Break functionality into subgenerators and compose with them; expose options to control behavior. Each subgenerator handles a distinct task—such as scaffolding files, configuring tooling, or adding dependencies—so you can reuse those pieces across different generators or projects and assemble them in different ways. Providing options lets callers tailor what gets generated without changing the internals, which is essential for adaptability. Yeoman supports composing generators, so you can plug in existing subgenerators and create new flows by orchestration rather than rewriting code. A monolithic generator makes reuse and maintenance hard; hard-coded templates lock you into one outcome; and hiding options prevents flexible use. Together, modular composition with configurable options yields generators that are easier to maintain, extend, and reuse.