Creating and removing directories in Node.js - Performance Optimization Steps

Performance: Creating and removing directories

MEDIUM IMPACT

This affects the file system operations impacting page load speed when server-side rendering or during build processes that create or remove directories.

Creating a directory during server runtime

Node.js

import { mkdir } from 'fs/promises';
await mkdir('./newDir');

Non-blocking asynchronous call allows other operations to continue while directory is created.

📈 Performance GainKeeps event loop free, improving server responsiveness

Creating a directory during server runtime

Node.js

const fs = require('fs');
fs.mkdirSync('./newDir');

Blocks the Node.js event loop until the directory is created, delaying other operations.

📉 Performance CostBlocks event loop, causing slower response times under load

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Synchronous directory operations	0 (server-side)	0	0	[X] Bad
Asynchronous directory operations	0 (server-side)	0	0	[OK] Good

Rendering Pipeline

Directory creation and removal are file system operations that do not directly affect browser rendering but impact server responsiveness and build times.

→Server Processing

→Build Time

⚠️ BottleneckBlocking synchronous file system calls delay server event loop and increase response time.

Optimization Tips

1Avoid synchronous directory operations in Node.js to prevent blocking the event loop.

2Use asynchronous fs.promises APIs with await for directory creation and removal.

3Blocking file system calls increase server response time but do not affect browser rendering directly.

Performance Quiz - 3 Questions

What is the main performance drawback of using synchronous directory creation in Node.js?

A It increases the size of the directory.

B It causes the browser to reflow the page.

C It blocks the event loop, delaying other operations.

D It reduces the server's memory usage.

DevTools: Performance

How to check: Record a server-side profiling session or use Node.js profiling tools to check event loop blocking during directory operations.

What to look for: Look for long blocking tasks or event loop delays indicating synchronous file system calls.

Practice

1. Which Node.js method is used to create a new directory?

easy

A. fs.createDir()

B. fs.rmdir()

C. fs.deleteDir()

D. fs.mkdir()

Solution

1. Step 1: Understand directory creation methods

   Node.js provides fs.mkdir() to create directories.

2. Step 2: Differentiate from removal methods

   fs.rmdir() is for removing directories, not creating.

3. Final Answer:

   fs.mkdir() -> Option D

4. Quick Check:

   Create directory = fs.mkdir() [OK]

Hint: Use fs.mkdir() to create folders, not fs.rmdir() [OK]

Common Mistakes:

• Confusing fs.mkdir() with fs.rmdir()
• Using non-existent fs.createDir()
• Trying to use fs.deleteDir() which doesn't exist

2. Which of the following is the correct syntax to create a nested directory parent/child in Node.js?

easy

A. fs.mkdir('parent/child', callback)

B. fs.mkdir('parent/child', { recursive: true }, callback)

C. fs.rmdir('parent/child', { recursive: true }, callback)

D. fs.mkdir('parent/child', { nested: true }, callback)

Solution

1. Step 1: Recognize recursive option for nested folders

   To create nested directories, use { recursive: true } option with fs.mkdir().

2. Step 2: Confirm correct method and options

   fs.mkdir with recursive true creates all needed folders; fs.rmdir is for removal, and nested option doesn't exist.

3. Final Answer:

   fs.mkdir('parent/child', { recursive: true }, callback) -> Option B

4. Quick Check:

   Nested folders need recursive: true [OK]

Hint: Use { recursive: true } with fs.mkdir for nested folders [OK]

Common Mistakes:

• Omitting recursive option for nested directories
• Using fs.rmdir instead of fs.mkdir
• Using incorrect option name like nested

3. What will happen if you run the following code snippet in Node.js?

const fs = require('fs');
fs.rmdir('myFolder', (err) => {
  if (err) console.log('Error:', err.message);
  else console.log('Folder removed');
});

Assuming myFolder contains files.

medium

A. Folder is removed successfully

B. Code throws a syntax error

C. Error logged because folder is not empty

D. Folder is renamed instead of removed

Solution

1. Step 1: Understand fs.rmdir behavior

   fs.rmdir only removes empty directories; if folder has files, it throws an error.

2. Step 2: Analyze error handling in callback

   The callback logs error message if removal fails due to non-empty folder.

3. Final Answer:

   Error logged because folder is not empty -> Option C

4. Quick Check:

   Non-empty folder removal = error [OK]

Hint: fs.rmdir fails if folder has files; must delete files first [OK]

Common Mistakes:

• Assuming fs.rmdir removes non-empty folders
• Expecting folder rename instead of removal
• Thinking code throws syntax error

4. Identify the error in this code snippet that tries to remove a directory:

const fs = require('fs');
fs.rmdir('testDir', { recursive: true }, (err) => {
  if (err) throw err;
  console.log('Directory removed');
});

medium

A. fs.rmdir does not support recursive option

B. Callback function is missing

C. fs.rmdir cannot remove directories

D. Directory path must be absolute

Solution

1. Step 1: Check fs.rmdir method options

   fs.rmdir does not support the recursive option; fs.rm should be used instead for recursive removal.

2. Step 2: Understand correct method for recursive removal

   Use fs.rm with { recursive: true } to remove non-empty directories recursively.

3. Final Answer:

   fs.rmdir does not support recursive option -> Option A

4. Quick Check:

   Recursive removal needs fs.rm, not fs.rmdir [OK]

Hint: Use fs.rm for recursive removal, not fs.rmdir [OK]

Common Mistakes:

• Using recursive option with fs.rmdir
• Thinking callback is missing
• Believing directory path must be absolute

5. You want to create a nested directory projects/app/src and then remove it completely including all files inside. Which sequence of Node.js methods should you use?

hard

A. Use fs.mkdir with { recursive: true } to create, then fs.rm with { recursive: true, force: true } to remove

B. Use fs.mkdir without options to create, then fs.rmdir to remove

C. Use fs.mkdir with { recursive: true } to create, then fs.rmdir to remove

D. Use fs.mkdir to create, then fs.unlink to remove

Solution

1. Step 1: Create nested directories

   Use fs.mkdir with { recursive: true } to create nested folders in one step.

2. Step 2: Remove directory with all contents

   Use fs.rm with { recursive: true, force: true } to delete directory and all files inside safely.

3. Final Answer:

   Use fs.mkdir with { recursive: true } to create, then fs.rm with { recursive: true, force: true } to remove -> Option A

4. Quick Check:

   Nested create + recursive remove = fs.mkdir + fs.rm [OK]

Hint: Create nested with mkdir recursive, remove all with rm recursive force [OK]

Common Mistakes:

• Using fs.rmdir to remove non-empty directories
• Omitting recursive option when creating nested folders
• Using fs.unlink which deletes files, not folders