Node.js installation and version management in Node.js - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Node.js Version Managers

Which of the following statements about Node.js version managers is correct?

A nvm allows you to install and switch between multiple Node.js versions on the same machine.

B nvm is a built-in Node.js command that updates Node.js automatically.

C nvm installs Node.js globally and does not support multiple versions.

D nvm is a package manager like npm used to install Node.js packages.

💡 Hint

Think about how developers manage different Node.js versions for different projects.

nvm (Node Version Manager) is a tool that lets you install and switch between multiple Node.js versions easily on the same computer.

📝 Syntax

intermediate

Correct Command to Install Node.js Version 18 Using nvm

Which command correctly installs Node.js version 18 using nvm?

A nvm install 18

B nvm use 18

C nvm setup 18

D nvm get 18

💡 Hint

Installing a version is different from switching to it.

The command nvm install 18 downloads and installs Node.js version 18. The nvm use 18 command switches to a version already installed.

❓ component_behavior

advanced

Behavior of Node.js Version After Switching with nvm

After running nvm install 16 and then nvm use 16, what will node -v output?

A v14.x.x (the default system Node.js version)

B v18.x.x (the latest Node.js version)

C Error: Node.js version not found

D v16.x.x (the exact installed version 16)

💡 Hint

The nvm use command sets the active Node.js version for the terminal session.

After installing and switching to version 16, node -v shows the exact version 16 installed.

🔧 Debug

advanced

Why Does 'node -v' Show a Different Version After Using nvm?

You installed Node.js 18 using nvm and ran nvm use 18. But running node -v still shows version 14. What is the most likely cause?

A The terminal session was not restarted or reloaded after running <code>nvm use 18</code>.

B Node.js 18 was not installed correctly by nvm.

C The <code>node</code> command is aliased to version 14 in your shell configuration.

D nvm does not support switching Node.js versions on your operating system.

💡 Hint

Check if your shell has any aliases or PATH settings overriding nvm.

If node is aliased or the PATH prioritizes another Node.js installation, node -v will show that version despite using nvm.

❓ state_output

expert

Result of Running Multiple nvm Commands Sequentially

Given the following commands run in order:
nvm install 14
nvm install 18
nvm use 14
node -v
What is the output of node -v?

A v18.x.x (Node.js version 18 active)

B v14.x.x (Node.js version 14 active)

C Error: No Node.js version active

D v16.x.x (some other version)

💡 Hint

The last nvm use command sets the active version.

After installing versions 14 and 18, the command nvm use 14 activates version 14, so node -v outputs version 14.