How can you create a generator that can be extended by others?

• A. Implement a base generator (class) and allow extension via standard Node inheritance or composition; publish as a base for extension
• B. Keep all logic private and non-extendable
• C. Avoid exporting APIs
• D. Require forks for extensions

Answer: (A)

The key idea is to provide a reusable base that others can extend, so they can build on common behavior instead of starting from scratch. By implementing a base generator as a class that extends Yeoman’s Generator and exporting it, you publish a well-defined extension point. Other developers can then create their own generator that inherits from this base (or composes it) and override or augment specific steps, such as prompting, configuring, or writing, while still reusing the shared logic. This approach makes extension straightforward, predictable, and maintainable, and you can document protected methods or hooks that are safe to customize.

Keeping all logic private or non-extendable blocks future customization and defeats reuse. Avoiding exported APIs prevents anyone from building on your work, and requiring forks is cumbersome and fractures the ecosystem—extension via inheritance or composition is the standard, scalable path.