In Yeoman, which statement best describes templatePath and destinationPath?

• A. templatePath points to source templates; destinationPath maps to the target path in the generated project
• B. destinationPath points to source templates; templatePath maps to target path
• C. They are interchangeable
• D. They are used only for copying binary files

Answer: (A)

In Yeoman, templatePath and destinationPath serve two distinct roles for file handling. templatePath resolves to the generator’s internal templates folder, where you store the source files you want to use as templates. destinationPath resolves to the target location inside the project you’re generating, i.e., the path in the new project where the processed file should be written.

So, templatePath points to source templates, while destinationPath specifies where those templates will go in the generated project. A common usage is combining them with a file operation like copyTpl: this.fs.copyTpl(this.templatePath('index.html'), this.destinationPath('src/index.html'), data). Here, the first argument is the absolute path to the template inside the generator, and the second is the path inside the generated project.

They’re not interchangeable because each refers to a different base location: one inside the generator’s templates, the other inside the output project. And they aren’t meant to imply binary-only copying; both helpers can be used for templated or plain copies depending on the method you call (e.g., copyTpl for templated text, copy for direct copies).