process.cwd and __dirname in Node.js - Step-by-Step Execution

Concept Flow - process.cwd and __dirname

Start Node.js script

↓

Read __dirname

→Returns script folder path

↓

Call process.cwd()

→Returns current working directory

↓

Use paths for file operations

↓

Script ends

The script starts, reads __dirname for script folder path, calls process.cwd() for current working directory, then uses these paths for file tasks.

Execution Sample

Node.js

console.log('__dirname:', __dirname);
console.log('process.cwd():', process.cwd());

Prints the folder path of the script and the current working directory where Node.js was started.

Execution Table

Step	Action	Value of __dirname	Value of process.cwd()	Output
1	Start script in /home/user/project/scripts	/home/user/project/scripts	/home/user/project/scripts	No output yet
2	Read __dirname	/home/user/project/scripts	/home/user/project/scripts	__dirname: /home/user/project/scripts
3	Call process.cwd()	/home/user/project/scripts	/home/user/project/scripts	process.cwd(): /home/user/project/scripts
4	Print both values	/home/user/project/scripts	/home/user/project/scripts	Printed both paths
5	Script ends	/home/user/project/scripts	/home/user/project/scripts	Execution complete

💡 Script ends after printing __dirname and process.cwd() values

Variable Tracker

Variable	Start	After Step 2	After Step 3	Final
__dirname	undefined	/home/user/project/scripts	/home/user/project/scripts	/home/user/project/scripts
process.cwd()	undefined	undefined	/home/user/project/scripts	/home/user/project/scripts

Key Moments - 2 Insights

Why are __dirname and process.cwd() different?

Because __dirname is the folder where the script file lives, while process.cwd() is the folder where you started Node.js. See execution_table steps 2 and 3.

Can process.cwd() change during script execution?

Yes, if you use process.chdir(), process.cwd() changes but __dirname stays the same. This is shown by how __dirname is fixed in step 2 but process.cwd() can vary.

Visual Quiz - 3 Questions

Look at the execution_table, what is the value of __dirname at step 3?

A /home/user/project/scripts

B /home/user/project

C undefined

D /home/user

💡 Hint

Check the __dirname column at step 3 in execution_table

At which step does process.cwd() get its value?

A Step 1

B Step 2

C Step 3

D Step 5

💡 Hint

Look at process.cwd() column in execution_table to see when it changes from undefined

If you start Node.js in /home/user/project/scripts, what will process.cwd() show?

A /home/user/project

B /home/user/project/scripts

C /home/user

D undefined

💡 Hint

process.cwd() shows the folder where Node.js was started, see variable_tracker and key_moments

Concept Snapshot

__dirname gives the folder path of the current script file.
process.cwd() gives the current working directory where Node.js was started.
They can be different if you run the script from another folder.
Use __dirname for script-relative paths.
Use process.cwd() for user working directory paths.
process.cwd() can change during runtime with process.chdir().

Full Transcript

When you run a Node.js script, __dirname holds the folder path where the script file is located. This never changes during the script. process.cwd() returns the current working directory where you started Node.js. This can be different from __dirname if you run the script from another folder. For example, if your script is in /home/user/project/scripts but you start Node.js from /home/user/project, __dirname will be /home/user/project/scripts and process.cwd() will be /home/user/project. You can use __dirname to access files relative to your script, and process.cwd() to access files relative to where the user started the program. process.cwd() can also change if you call process.chdir() during the script. This trace shows step-by-step how these values are read and printed.