NestJS CLI installation - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the NestJS CLI used for?

The NestJS CLI is a tool that helps you create, develop, and manage NestJS projects easily from the command line.

beginner

Which command installs the NestJS CLI globally using npm?

You install the NestJS CLI globally by running: npm install -g @nestjs/cli

beginner

Why do we install the NestJS CLI globally?

Installing globally lets you run the nest command anywhere on your computer, making it easy to create and manage projects.

beginner

What command creates a new NestJS project after installing the CLI?

Use nest new project-name to create a new NestJS project with the CLI.

beginner

How can you check if the NestJS CLI is installed correctly?

Run nest --version in your terminal. If it shows a version number, the CLI is installed correctly.

Which command installs the NestJS CLI globally?

A npm install nestjs

B npm install @nestjs/core

C nest install cli

D npm install -g @nestjs/cli

The correct command to install the NestJS CLI globally is npm install -g @nestjs/cli.

What does the command nest new my-app do?

A Creates a new NestJS project named my-app

B Updates the NestJS CLI

C Installs NestJS dependencies

D Runs the NestJS server

The command nest new my-app creates a new NestJS project folder called my-app.

How do you verify the NestJS CLI is installed?

A npm version nestjs

B nest --version

C nest check

D npm list nestjs

Running nest --version shows the installed CLI version if it is installed.

Why install the NestJS CLI globally?

A To install NestJS core libraries

B To limit usage to one project

C To use the nest command anywhere on your computer

D To update Node.js

Global installation allows running the nest command from any folder.

Which package manager is commonly used to install the NestJS CLI?

A npm

B pip

C gem

D composer

npm is the Node.js package manager used to install NestJS CLI.

Explain the steps to install the NestJS CLI and create a new project.

Think about commands you type in the terminal.

Why is it helpful to install the NestJS CLI globally instead of locally?

Consider how global tools work on your computer.

Practice

1. What is the main purpose of the NestJS CLI?

easy

A. To help create and manage NestJS projects easily

B. To run NestJS applications in production

C. To replace Node.js runtime

D. To write CSS styles for NestJS apps

Solution

1. Step 1: Understand what CLI tools do

   CLI tools help automate tasks like creating and managing projects.

2. Step 2: Match NestJS CLI purpose

   NestJS CLI specifically helps start and manage NestJS projects quickly.

3. Final Answer:

   To help create and manage NestJS projects easily -> Option A

4. Quick Check:

   NestJS CLI = project management tool [OK]

Hint: CLI means command line helper for projects [OK]

Common Mistakes:

• Thinking CLI runs the app in production
• Confusing CLI with runtime environment
• Assuming CLI styles the app

2. Which command correctly installs the NestJS CLI globally using npm?

easy

A. npm install nestjs-cli

B. npm install -g @nestjs/cli

C. npm global add nestjs

D. npm install @nestjs/cli

Solution

1. Step 1: Identify npm global install syntax

   Global install uses npm install -g package-name.

2. Step 2: Match correct package name

   The official NestJS CLI package is @nestjs/cli.

3. Final Answer:

   npm install -g @nestjs/cli -> Option B

4. Quick Check:

   Global install = npm install -g @nestjs/cli [OK]

Hint: Global npm installs use -g flag [OK]

Common Mistakes:

• Omitting the -g flag for global install
• Using wrong package name
• Using npm global add instead of install -g

3. After installing NestJS CLI globally, what happens when you run nest new my-app?

medium

A. It deletes the 'my-app' folder if it exists

B. It runs the NestJS server immediately

C. It creates a new NestJS project folder named 'my-app'

D. It updates the NestJS CLI to the latest version

Solution

1. Step 1: Understand the nest new command

   This command creates a new project folder with starter files.

2. Step 2: Analyze the argument 'my-app'

   The argument specifies the folder name for the new project.

3. Final Answer:

   It creates a new NestJS project folder named 'my-app' -> Option C

4. Quick Check:

   nest new = create project folder [OK]

Hint: nest new always creates a new project folder [OK]

Common Mistakes:

• Thinking it runs the server immediately
• Assuming it updates CLI version
• Believing it deletes folders

4. You run npm install -g nestjs/cli but get an error. What is the likely problem?

medium

A. You must use yarn instead of npm

B. You forgot to add the -g flag for global install

C. You need to run the command inside a NestJS project folder

D. The package name is incorrect; it should be '@nestjs/cli'

Solution

1. Step 1: Check the package name format

   Correct package name uses the scope '@nestjs/cli', not 'nestjs/cli'.

2. Step 2: Understand npm package naming

   Scoped packages start with '@' and are required for correct install.

3. Final Answer:

   The package name is incorrect; it should be '@nestjs/cli' -> Option D

4. Quick Check:

   Correct package name = @nestjs/cli [OK]

Hint: Scoped packages start with @ symbol [OK]

Common Mistakes:

• Using slash instead of @ for scoped package
• Forgetting -g flag (but question says it is present)
• Thinking install must be inside project folder

5. You want to install NestJS CLI globally but only for your current user without admin rights. Which command should you use?

hard

A. npm install -g @nestjs/cli --prefix ~/.npm-global

B. npm install @nestjs/cli

C. npm install -g @nestjs/cli

D. npm install --save @nestjs/cli

Solution

1. Step 1: Understand global install without admin rights

   Global install usually needs admin rights; using --prefix installs globally in user folder.

2. Step 2: Match command with user-level global install

   Using npm install -g @nestjs/cli --prefix ~/.npm-global installs CLI globally for current user only.

3. Final Answer:

   npm install -g @nestjs/cli --prefix ~/.npm-global -> Option A

4. Quick Check:

   User-level global install = npm install -g with --prefix [OK]

Hint: Use --prefix to install global packages without admin rights [OK]

Common Mistakes:

• Using normal install without -g for global tools
• Trying to install globally without admin rights and no prefix
• Confusing --save with global install