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.

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