How do you perform async operations in a Yeoman generator?

• A. Use setTimeout with a fixed delay
• B. Always use synchronous methods
• C. You cannot perform async operations
• D. Return a promise or call this.async() to get a done callback

Answer: (D)

Asynchronous work in a Yeoman generator is coordinated by signaling when that work is finished. Yeoman runs each generator method in order, and if a method starts async tasks, it must tell Yeoman when those tasks are done so the next step can run at the right time. The right approach is to either return a promise (or use async/await, which returns a promise) or call this.async() to obtain a done callback and invoke it when the async work completes.

Returning a promise lets Yeoman wait automatically for the operation to finish before proceeding. Using async/await inside a method is a clean way to express that flow, and returning the final result (or letting the function be async) signals completion as well. Alternatively, this.async() gives you a done callback; you perform your async work and call done() when finished. This pattern is useful when you’re working with APIs that don’t return promises or when you need explicit control over when the step ends.

This approach is preferred because it ensures the generator doesn’t move on too early or hang while awaiting real asynchronous tasks. Relying on a fixed delay with setTimeout can lead to race conditions and flaky behavior, and insisting on synchronous methods isn’t practical for IO, prompts, or network requests. Yes, you can perform async operations in a Yeoman generator, and signaling completion with a promise or a done callback is the recommended way.