path.extname for file extensions in Node.js - Performance & Optimization

Performance: path.extname for file extensions

LOW IMPACT

This affects the speed of extracting file extensions during file path processing, impacting script execution time.

Extracting file extension from a file path

Node.js

const ext = path.extname(filename);

Uses optimized native code to extract extension without creating intermediate arrays.

📈 Performance Gainreduces CPU and memory usage, faster for many calls

Extracting file extension from a file path

Node.js

const ext = filename.split('.').pop();

Splitting the string and popping the last element creates unnecessary array objects and can be slower for many calls.

📉 Performance Costcreates extra array objects per call, minor CPU overhead

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
String.split + pop	0	0	0	[X] Bad
path.extname	0	0	0	[OK] Good

Rendering Pipeline

This concept is about JavaScript execution speed and memory usage during file path processing, not browser rendering.

→JavaScript Execution

⚠️ BottleneckString manipulation and memory allocation during splitting

Optimization Tips

1Use native path.extname to extract file extensions efficiently.

2Avoid splitting strings repeatedly to reduce CPU and memory overhead.

3File extension extraction does not impact browser rendering metrics directly.

Performance Quiz - 3 Questions

Why is using path.extname better than splitting a string to get a file extension?

A It caches all file extensions automatically.

B It uses optimized native code and avoids creating extra arrays.

C It modifies the original filename to be shorter.

D It blocks the event loop for faster execution.

DevTools: Performance

How to check: Record a CPU profile while running code that extracts file extensions many times; compare time spent in string.split vs path.extname calls.

What to look for: Lower CPU time and fewer memory allocations indicate better performance with path.extname.

Practice

1. What does path.extname('example.txt') return in Node.js?

easy

A. '.txt'

B. 'txt'

C. 'example.txt'

D. '' (empty string)

Solution

1. Step 1: Understand what path.extname does

   The path.extname method extracts the file extension including the dot from a filename string.

2. Step 2: Apply to 'example.txt'

   Since the file name is 'example.txt', the extension is '.txt' including the dot.

3. Final Answer:

   '.txt' -> Option A

4. Quick Check:

   Extension includes dot = '.txt' [OK]

Hint: Remember extname returns extension with dot [OK]

Common Mistakes:

• Forgetting the dot in the extension
• Returning the whole filename
• Returning empty string for files with extension

2. Which of the following is the correct syntax to get the extension of a file named 'photo.jpeg' using Node.js path module?

easy

A. path.extname('photo.jpeg')

B. path.extension('photo.jpeg')

C. path.getExt('photo.jpeg')

D. path.ext('photo.jpeg')

Solution

1. Step 1: Recall the correct method name

   The Node.js path module provides the method extname to get file extensions.

2. Step 2: Check the syntax

   The correct syntax is path.extname('filename'). Other options are invalid method names.

3. Final Answer:

   path.extname('photo.jpeg') -> Option A

4. Quick Check:

   Correct method is extname() [OK]

Hint: Use path.extname() exactly as named [OK]

Common Mistakes:

• Using incorrect method names like extension or ext
• Missing parentheses after method name
• Confusing with other path methods

3. What will be the output of the following code?

const path = require('path');
console.log(path.extname('archive.tar.gz'));

medium

A. '.tar.gz'

B. '' (empty string)

C. 'tar.gz'

D. '.gz'

Solution

1. Step 1: Understand how extname handles multiple dots

   The path.extname method returns the substring from the last dot to the end of the string.

2. Step 2: Apply to 'archive.tar.gz'

   The last dot is before 'gz', so the extension returned is '.gz'.

3. Final Answer:

   '.gz' -> Option D

4. Quick Check:

   Extension is from last dot = '.gz' [OK]

Hint: extname returns from last dot to end [OK]

Common Mistakes:

• Assuming it returns multiple extensions
• Returning empty string for multiple dots
• Including the whole suffix after first dot

4. Identify the error in this code snippet:

const path = require('path');
const ext = path.extname('document');
console.log(ext);

medium

A. It returns 'document' as extension

B. It throws an error because 'document' has no extension

C. It returns an empty string because no extension exists

D. It returns undefined

Solution

1. Step 1: Check the filename for extension

   The filename 'document' has no dot, so no extension exists.

2. Step 2: Understand extname behavior with no extension

   path.extname returns an empty string when no extension is found, not an error or undefined.

3. Final Answer:

   It returns an empty string because no extension exists -> Option C

4. Quick Check:

   No dot means empty string [OK]

Hint: No dot means extname returns empty string [OK]

Common Mistakes:

• Expecting an error for missing extension
• Expecting undefined instead of empty string
• Confusing filename with extension

5. You want to filter an array of filenames to only include '.js' files. Which code snippet correctly uses path.extname to do this?

const path = require('path');
const files = ['app.js', 'index.html', 'script.ts', 'readme'];
const jsFiles = files.filter(???);
console.log(jsFiles);

hard

A. file => path.extname(file) === ''

B. file => path.extname(file) === '.js'

C. file => path.extname(file) === '.JS'

D. file => path.extname(file) === 'js'

Solution

1. Step 1: Understand the filter condition

   We want to keep files whose extension is exactly '.js' including the dot and case-sensitive.

2. Step 2: Use path.extname correctly

   The correct comparison is path.extname(file) === '.js'. Other options either miss the dot, use wrong case, or check for empty extension.

3. Final Answer:

   file => path.extname(file) === '.js' -> Option B

4. Quick Check:

   Filter by exact '.js' extension [OK]

Hint: Compare extname result including dot and case [OK]

Common Mistakes:

• Omitting the dot in extension comparison
• Ignoring case sensitivity
• Filtering by empty string instead of '.js'