Project scaffolding in NestJS - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a new NestJS project using the CLI.

NestJS

nest [1] my-nest-app

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

Abuild

Bnew

Cstart

Dgenerate

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'start' instead of 'new' which runs the app instead of creating it.

Using 'build' which compiles code but does not create a project.

The nest new command initializes a new NestJS project with the given name.

2fill in blank

medium

Complete the command to add a new module named 'users' to your NestJS project.

NestJS

nest [1] module users

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

Acreate

Bstart

Cbuild

Dgenerate

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'create' which is for new projects, not parts inside a project.

Using 'start' which runs the app instead of generating files.

The nest generate command is used to create new components like modules, controllers, or services.

3fill in blank

hard

Fix the error in the command to generate a controller named 'auth'.

NestJS

nest generate [1] auth

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

Acontroller

Bservice

Cmodule

Dapp

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'service' which generates a service, not a controller.

Using 'module' which generates a module, not a controller.

To generate a controller, you must specify controller after generate.

4fill in blank

hard

Fill both blanks to generate a service named 'payment' inside the 'orders' module.

NestJS

nest generate [1] payment --module [2]

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

Aservice

Bcontroller

Corders

Dusers

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'controller' instead of 'service' for the first blank.

Using the wrong module name in the second blank.

You generate a service and specify the orders module to place it inside.

5fill in blank

hard

Fill all three blanks to generate a controller named 'profile' with a spec file inside the 'users' module.

NestJS

nest generate [1] profile --module [2] --[3]

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

Acontroller

Busers

Cspec

Dservice

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'service' instead of 'controller' for the first blank.

Forgetting to specify the module name.

Omitting the '--spec' flag to generate test files.

You generate a controller named 'profile' inside the users module and include a spec file for testing.

Practice

1. What is the main purpose of using nest new project-name in NestJS?

easy

A. To create a new NestJS project with a ready-to-use structure

B. To start the NestJS development server

C. To install NestJS dependencies globally

D. To generate a new module inside an existing project

Solution

1. Step 1: Understand the command nest new project-name

   This command is used to create a new NestJS project folder with all necessary files and folders set up.

2. Step 2: Identify the purpose of scaffolding

   Scaffolding means generating a basic project structure automatically to save time and follow best practices.

3. Final Answer:

   To create a new NestJS project with a ready-to-use structure -> Option A

4. Quick Check:

   Project scaffolding = create new project structure [OK]

Hint: Remember: 'nest new' creates a fresh project folder fast [OK]

Common Mistakes:

• Confusing 'nest new' with starting the server
• Thinking it installs global packages only
• Mixing it up with generating modules inside projects

2. Which of the following is the correct syntax to create a new NestJS project named my-app?

easy

A. nest create my-app

B. nest new my-app

C. nest generate project my-app

D. nest init my-app

Solution

1. Step 1: Recall the NestJS CLI command for new projects

   The official command to scaffold a new project is nest new project-name.

2. Step 2: Match the correct syntax

   Among the options, only nest new my-app matches the correct CLI command format.

3. Final Answer:

   nest new my-app -> Option B

4. Quick Check:

   Correct CLI syntax = nest new [OK]

Hint: Use 'nest new' exactly to scaffold projects [OK]

Common Mistakes:

• Using 'nest create' instead of 'nest new'
• Trying 'nest generate project' which is invalid
• Confusing 'nest init' with project creation

3. After running nest new sample-app, which folder structure will you see inside sample-app?

medium

A. src/, node_modules/, package.json, nest-cli.json

B. app/, config/, public/, package-lock.json

C. controllers/, models/, views/, app.js

D. lib/, bin/, config/, README.md

Solution

1. Step 1: Recall default NestJS project folders

   A new NestJS project contains a src/ folder for source code, node_modules/ for dependencies, and config files like package.json and nest-cli.json.

2. Step 2: Compare options with known structure

   src/, node_modules/, package.json, nest-cli.json matches the expected NestJS scaffold structure; others list unrelated folders or files.

3. Final Answer:

   src/, node_modules/, package.json, nest-cli.json -> Option A

4. Quick Check:

   Default NestJS scaffold = src and config files [OK]

Hint: Look for src folder and package.json in new projects [OK]

Common Mistakes:

• Expecting MVC folders like controllers, models, views
• Confusing with frontend project structures
• Looking for app.js which is not used in NestJS

4. You ran nest new myproject but got an error: Command 'nest' not found. What is the most likely fix?

medium

A. Rename the folder to 'nest' before running the command

B. Run nest new inside an existing NestJS project

C. Use npm start instead of nest new

D. Install Nest CLI globally using npm i -g @nestjs/cli

Solution

1. Step 1: Understand the error meaning

   The error means the system does not recognize the nest command, likely because the Nest CLI is not installed globally.

2. Step 2: Identify the correct fix

   Installing the Nest CLI globally with npm i -g @nestjs/cli makes the nest command available anywhere.

3. Final Answer:

   Install Nest CLI globally using npm i -g @nestjs/cli -> Option D

4. Quick Check:

   Missing CLI = install globally [OK]

Hint: Install Nest CLI globally to use 'nest' command [OK]

Common Mistakes:

• Trying to run 'nest new' inside a non-NestJS folder
• Using npm start which runs app, not CLI
• Renaming folders instead of installing CLI

5. You want to create a new NestJS project but customize the package manager to use yarn instead of npm. Which command should you run?

hard

A. nest new myapp --package yarn

B. nest new myapp --use-yarn

C. nest new myapp --package-manager yarn

D. nest new myapp --pm yarn

Solution

1. Step 1: Recall NestJS CLI option for package manager

   The Nest CLI supports the option --package-manager to specify which package manager to use during project creation.

2. Step 2: Match the correct option syntax

   nest new myapp --package-manager yarn uses the correct full option --package-manager yarn. Other options are invalid or incomplete.

3. Final Answer:

   nest new myapp --package-manager yarn -> Option C

4. Quick Check:

   Use --package-manager to set yarn [OK]

Hint: Use --package-manager option to pick yarn or npm [OK]

Common Mistakes:

• Using shorthand or incorrect flags like --pm or --use-yarn
• Assuming default is yarn without specifying
• Trying --package instead of --package-manager