NestJS CLI installation - Practice Problems & Coding Challenges

Challenge - 5 Problems

📝 Syntax

intermediate

Correct command to install NestJS CLI globally

Which command correctly installs the NestJS CLI globally using npm?

A npm install -g @nestjs/cli

B npm install @nestjs/cli -g

C npm global install @nestjs/cli

D npm install --global nestjs-cli

💡 Hint

The global flag should come immediately after 'install'.

The correct syntax to install a package globally with npm is npm install -g package-name. Option A uses this syntax correctly for the NestJS CLI package @nestjs/cli.

❓ component_behavior

intermediate

Behavior after installing NestJS CLI globally

After installing NestJS CLI globally, what happens when you run nest --version in the terminal?

A It throws an error saying 'command not found'.

B It creates a new NestJS project in the current folder.

C It opens the NestJS documentation in the browser.

D It shows the installed NestJS CLI version number.

💡 Hint

The --version flag usually shows version info for CLI tools.

Running nest --version after a successful global install displays the version of the NestJS CLI installed. It does not create projects or open docs.

🔧 Debug

advanced

Troubleshooting 'nest' command not found after global install

You installed NestJS CLI globally with npm install -g @nestjs/cli, but running nest gives 'command not found'. What is the most likely cause?

A The NestJS CLI package is deprecated and no longer works.

B You need to restart your computer before using new global commands.

C The global npm bin folder is not in your system PATH environment variable.

D You must run <code>npm link @nestjs/cli</code> after installation.

💡 Hint

Global commands require the system to know where to find them.

If the global npm bin folder is not in your PATH, the shell cannot find the nest command. Restarting or linking is not required, and the package is actively maintained.

🧠 Conceptual

advanced

Understanding local vs global NestJS CLI installation

What is the main difference between installing NestJS CLI globally vs locally in a project?

A Global install allows using <code>nest</code> command anywhere; local install restricts usage to that project only.

B Local install automatically updates the CLI; global install does not.

C Global install requires root permissions; local install does not.

D Local install installs the CLI as a system service; global install does not.

💡 Hint

Think about where you can run the nest command after each install type.

Global installation makes the CLI command available in any terminal location. Local installation installs it only inside the project folder, so you must run it via npx nest or scripts.

❓ state_output

expert

Output of NestJS CLI project creation command

What output do you expect immediately after running nest new my-app in a terminal with NestJS CLI installed globally?

A An error saying 'Project name missing' is shown.

B A new folder 'my-app' is created with initial NestJS project files and a prompt to choose package manager.

C The CLI installs global dependencies but does not create any folder.

D The terminal opens the NestJS website for project templates.

💡 Hint

The nest new command scaffolds a new project folder.

Running nest new my-app creates a new folder named 'my-app' with starter files and asks which package manager to use. It does not show errors or open websites.