Name a common pitfall when writing templates in a generator.

• A. Hard-coding paths or failing to use templatePath/destinationPath leading to wrong file locations
• B. Relying on this.templatePath and this.destinationPath to resolve paths
• C. Not using path.join and templatePath to construct paths
• D. Overriding templates with custom logic

Answer: (A)

When writing templates for a generator, handling file paths carefully is essential. A very common pitfall is hard-coding where files go or failing to use the generator’s path helpers like templatePath and destinationPath. If you hard-code paths, the generator becomes brittle: it may place files in the wrong folders, break when the project layout is different, or fail on different operating systems or when run from another location. Using templatePath to locate templates and destinationPath to determine where to write files keeps everything predictable and portable, because these helpers resolve paths relative to the generator’s templates and the user’s project root. It’s also important to build paths with path.join to ensure cross-platform compatibility. So, the most frequent issue is relying on fixed paths instead of the proper path resolution the generator provides, which is what leads to incorrect file locations.