NestJS CLI installation - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to install NestJS CLI globally using npm.

NestJS

npm install -g [1]

Drag options to blanks, or click blank then click option'

A@nestjs/cli

Bnestjs-cli

Cnest-cli

Dnestjs

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'nestjs-cli' or 'nest-cli' which are not the official package names.

Installing 'nestjs' which is not the CLI tool.

The correct package to install the NestJS CLI globally is @nestjs/cli. This allows you to use the nest command anywhere on your system.

2fill in blank

medium

Complete the command to check the installed NestJS CLI version.

NestJS

nest [1]

Drag options to blanks, or click blank then click option'

A-v

Blist

Cversion

D--version

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'nest --version' which is valid but not the expected answer here.

Using 'nest list' which lists commands, not version.

The command nest -v shows the installed NestJS CLI version. The -v flag is a common shorthand for version.

3fill in blank

hard

Fix the error in the command to install NestJS CLI locally as a dev dependency.

NestJS

npm install [1] --save-dev

Drag options to blanks, or click blank then click option'

Anestjs-cli

Bnestjs

Cnest-cli

D@nestjs/cli

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'nestjs' which is not the CLI package.

Using 'nest-cli' or 'nestjs-cli' which are incorrect package names.

The correct package to install locally as a dev dependency is @nestjs/cli. This installs the official NestJS CLI in your project.

4fill in blank

hard

Fill both blanks to create a new NestJS project named 'my-app' using the CLI.

NestJS

nest [1] [2]

Drag options to blanks, or click blank then click option'

Anew

Bcreate

Cmy-app

Dapp

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'create' instead of 'new' for the command.

Using 'app' instead of the intended project name.

The command to create a new project is nest new my-app. The new keyword tells the CLI to create a project, and my-app is the project name.

5fill in blank

hard

Fill all three blanks to install NestJS CLI globally using yarn and verify its version.

NestJS

yarn global [1] [2] && nest [3]

Drag options to blanks, or click blank then click option'

Ainstall

B@nestjs/cli

C-v

Dadd

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'install' instead of 'add' for yarn global command.

Using incorrect package names.

Using '--version' instead of '-v' for version check.

To install the NestJS CLI globally with yarn, use yarn global add @nestjs/cli. Then, check the version with nest -v.

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