Running JavaScript using Node.js - Step-by-Step Execution

Concept Flow - Running JavaScript using Node.js

Write JavaScript file (e.g., script.js)

↓

Open terminal or command prompt

↓

Run command: node script.js

↓

Node.js reads and executes the file

↓

Output appears in terminal

↓

Program ends

This flow shows how you write a JavaScript file, run it with Node.js in the terminal, and see the output.

Execution Sample

Javascript

console.log('Hello from Node.js!');

This code prints a message to the terminal when run with Node.js.

Execution Table

Step	Action	Evaluation	Result
1	Start Node.js with script.js	Node.js loads script.js	Ready to execute
2	Execute console.log	Print string 'Hello from Node.js!'	Message shown in terminal
3	End of script	No more code	Program exits

💡 Script finishes after printing the message; Node.js process ends

Variable Tracker

Variable	Start	After Step 2	Final
console	object	object	object
console.log	function	function	function

Key Moments - 2 Insights

Why do I run 'node script.js' in the terminal?

Running 'node script.js' tells Node.js to read and execute your JavaScript file, as shown in execution_table step 1.

Why does the output appear in the terminal and not in a browser?

Node.js runs JavaScript outside the browser and prints output directly to the terminal, as seen in execution_table step 2.

Visual Quiz - 3 Questions

Look at the execution table, what happens at step 2?

A Node.js reads the file

B The message is printed to the terminal

C The program exits

D The terminal opens

💡 Hint

Check the 'Result' column in step 2 of the execution_table

At which step does the program finish running?

A Step 1

B Step 2

C Step 3

D After step 3

💡 Hint

Look at the 'Action' and 'Result' columns in the execution_table for when the program ends

If you change the message inside console.log, what changes in the execution?

A The output message in the terminal changes

B The program will not run

C Node.js will crash

D The terminal will not open

💡 Hint

Refer to the 'Evaluation' and 'Result' columns in step 2 of the execution_table

Concept Snapshot

Running JavaScript with Node.js:
1. Write your code in a .js file.
2. Open terminal and run 'node filename.js'.
3. Node.js executes the file and prints output to terminal.
4. Program ends when code finishes.
Use terminal to see results outside browser.

Full Transcript

To run JavaScript using Node.js, first write your JavaScript code in a file with a .js extension, for example, script.js. Then open your terminal or command prompt. Run the command 'node script.js' to start Node.js and execute your file. Node.js reads the file and runs the code inside. If your code uses console.log, the message will appear in the terminal. After the code finishes running, the Node.js process ends. This lets you run JavaScript outside a browser and see output directly in the terminal.

Practice

1. What does the command node filename.js do?

easy

A. Runs the JavaScript code inside filename.js using Node.js

B. Opens the file filename.js in a text editor

C. Compiles filename.js into a different programming language

D. Deletes the file filename.js from your computer

Solution

1. Step 1: Understand the command node filename.js

   This command tells Node.js to run the JavaScript code inside the file named filename.js.

2. Step 2: Identify what Node.js does

   Node.js executes JavaScript code outside the browser, so it runs the code in the file.

3. Final Answer:

   Runs the JavaScript code inside filename.js using Node.js -> Option A

4. Quick Check:

   node filename.js runs code = C [OK]

Hint: Node runs JavaScript files given after the command [OK]

Common Mistakes:

• Thinking it opens the file in an editor
• Confusing running with compiling
• Assuming it deletes the file

2. Which of the following is the correct way to start an interactive Node.js session in the terminal?

easy

A. run node

B. node filename.js

C. node

D. start node.js

Solution

1. Step 1: Recall how to start Node.js interactively

   Typing node alone in the terminal starts an interactive JavaScript session.

2. Step 2: Check other options

   node filename.js runs a file, not interactive mode; run node and start node.js are invalid commands.

3. Final Answer:

   node -> Option C

4. Quick Check:

   Just node starts interactive mode [OK]

Hint: Just type 'node' to enter interactive mode [OK]

Common Mistakes:

• Adding extra words like 'run' or 'start'
• Confusing running a file with interactive mode
• Using file names when none are needed

3. What will be the output when running this file with node test.js?

console.log('Hello from Node.js!');

medium

A. SyntaxError

B. Hello from Node.js!

C. undefined

D. No output

Solution

1. Step 1: Understand the code inside test.js

   The code uses console.log to print a string to the console.

2. Step 2: Know what Node.js does when running the file

   Node.js executes the code and prints the string to the terminal.

3. Final Answer:

   Hello from Node.js! -> Option B

4. Quick Check:

   console.log prints text = Hello from Node.js! [OK]

Hint: console.log prints output to terminal [OK]

Common Mistakes:

• Expecting no output
• Confusing console.log with return value
• Thinking it causes an error

4. You try to run node app.js but get an error: SyntaxError: Unexpected token. What is the most likely cause?

medium

A. You typed node incorrectly

B. You forgot to save app.js before running

C. Node.js is not installed on your computer

D. The app.js file has invalid JavaScript syntax

Solution

1. Step 1: Understand the error message

   A SyntaxError: Unexpected token means the JavaScript code has a syntax mistake.

2. Step 2: Check other options

   Typing node wrong usually gives a different error; missing Node.js causes 'command not found'; unsaved file won't run but usually no syntax error.

3. Final Answer:

   The app.js file has invalid JavaScript syntax -> Option D

4. Quick Check:

   SyntaxError means code syntax is wrong [OK]

Hint: SyntaxError means code inside file is wrong [OK]

Common Mistakes:

• Assuming Node.js is missing
• Thinking the command was typed wrong
• Not saving file before running

5. You want to quickly test a small JavaScript expression without creating a file. What is the best way to do this using Node.js?

hard

A. Run node in terminal to open interactive mode and type the expression

B. Create a file, write the code, then run node filename.js

C. Use npm start to run the expression

D. Open a browser and run the code in the console

Solution

1. Step 1: Identify how to run code without a file

   Running node alone opens an interactive session where you can type JavaScript directly.

2. Step 2: Compare other options

   Creating a file is slower; npm start runs scripts defined in package.json, not quick tests; browser console is outside Node.js environment.

3. Final Answer:

   Run node in terminal to open interactive mode and type the expression -> Option A

4. Quick Check:

   Interactive mode = quick testing [OK]

Hint: Use just 'node' to test code quickly without files [OK]

Common Mistakes:

• Thinking npm start runs any code
• Believing browser console is Node.js
• Always creating files for small tests