use-template

Yes, npm is required to set up a cloned game template because the tool executes npm install during the cloning process. This automatically fetches and installs all project dependencies defined in the template's package.json.

To scaffold a game project from a starter template, provide a template-id and optional project-name. The tool copies the template files, updates package.json and index.html titles, excludes build artifacts, and runs npm install automatically to finish setup.

Yes, you can clone a game template as a standalone project outside the game-creator repository. The tool automatically detects your current directory context and determines the correct target path for the new project folder accordingly.

When cloning a template to a new project directory, noisy build artifacts like node_modules and build outputs are excluded. This ensures a clean copy of the starter project, requiring a fresh npm install to fetch dependencies.

The template clone process validates the provided project-name to prevent path traversal vulnerabilities. This security check ensures the new project directory is created safely within the intended target scope without escaping the file system boundaries.

Yes, npm is required to set up a cloned game template because the tool executes npm install during the cloning process. This automatically fetches and installs all project dependencies defined in the template's package.json.