Setting Up Node.js and Express.js Environment

# CHAPTER 2

Setting Up Node.js and Express.js Environment #

1. Introduction #

2. Learning Objectives #

• Install Node.js and verify the installation in the terminal.

• Initialize a project using npm init.

• Install the express package via NPM.

• Understand the role of package.json and node_modules.

3. Beginner-Friendly Explanation #

1. 1. First, you need the console (PlayStation/Xbox). Node.js is the console. It is the machine that physically runs the code.

1. 2. Next, you need a store to download the games. NPM (Node Package Manager) is the digital store.

1. 3. Finally, you need the actual game. Express.js is the game you download from the store to play on the console.

In backend development, you install the Node.js console once. Then, for every new project, you use NPM to download the Express framework.

4. Step 1: Installing Node.js #

1. 1. Visit the official website: nodejs.org.

1. 2. Download the LTS (Long Term Support) version. This is the most stable version and is recommended for all production applications.

1. 3. Run the installer and click "Next" through the default options.

Verify the Installation: Open your Terminal (Mac/Linux) or Command Prompt/PowerShell (Windows) and type:

node -v

*(This will print the installed version, e.g., v20.x.x).*

Node.js automatically installs NPM. Verify it by typing:

npm -v

5. Step 2: Initializing the Project #

mkdir express-app
cd express-app

Now, initialize the project to create a package.json file:

npm init -y

The package.json file is the ID card of your project. It records the project name and keeps a list of every third-party package you install.

6. Step 3: Installing Express.js #

npm install express

What just happened?

1. 1. NPM connected to the internet and downloaded the Express codebase.

1. 2. It created a folder called node_modules and placed the code inside.

1. 3. It updated your package.json file to record that "Express" is now a dependency.

7. Step 4: Installing Nodemon (Development Tool) #

npm install nodemon --save-dev

*(The --save-dev flag means we only use this tool for local development, not on the live server).*

8. Step 5: Updating Scripts #

"scripts": {
  "start": "node index.js",
  "dev": "nodemon index.js"
}

Now, to start your server, you simply type npm run dev in the terminal!

9. Standard Project Structure #

• models/: Database schemas (e.g., User, Post).

• controllers/: Business logic.

• routes/: URL definitions.

• middleware/: Custom security or validation functions.

• index.js or app.js: The main entry point of the server.

10. Best Practices #

• The .gitignore File: If you use Git/GitHub, you MUST create a .gitignore file and type node_modules/ inside it. The node_modules folder contains thousands of files and is massive. You never upload it. Because your package.json remembers what you installed, another developer simply types npm install and Node rebuilds the folder for them automatically.

11. Common Mistakes #

• Forgetting npm init: If you try to run npm install express without first running npm init, NPM won't know where to save the dependency record. Always initialize the project first.

12. Exercises #

1. 1. Explain the difference between npm install express and npm install nodemon --save-dev.

13. Coding Challenges #

• Challenge: Open your terminal, create a folder named api-challenge, initialize it with npm init -y, install express, and write a dev script in the package.json that uses nodemon.

14. MCQs with Answers #

15. Interview Questions #

• Q: Explain the purpose of the node_modules directory. Why is it standard practice to exclude it from version control (Git)?

• Q: What is the difference between a standard dependency and a devDependency in Node.js? Give an example of a package that belongs in each.

16. FAQs #

17. Summary #

18. Next Chapter Recommendation #