Bird
Raised Fist0
Node.jsframework~15 mins

path.parse and path.format in Node.js - Mini Project: Build & Apply

Choose your learning style10 modes available

Start learning this pattern below

Jump into concepts and practice - no test required

or
Recommended
Test this pattern10 questions across easy, medium, and hard to know if this pattern is strong
Using path.parse and path.format in Node.js
📖 Scenario: You are working on a Node.js project where you need to break down file paths into parts and then rebuild them after making some changes.
🎯 Goal: Learn how to use path.parse to split a file path into its components and path.format to join those components back into a path string.
📋 What You'll Learn
Create a string variable with a file path
Use path.parse to split the path into parts
Modify one part of the parsed path
Use path.format to rebuild the path string
💡 Why This Matters
🌍 Real World
Breaking down and rebuilding file paths is common when managing files, renaming files, or changing file locations in Node.js applications.
💼 Career
Understanding how to manipulate file paths is important for backend developers working with file systems, scripts, and server-side applications.
Progress0 / 4 steps
1
Create a file path string
Create a variable called filePath and set it to the string "/home/user/docs/report.txt".
Node.js
Hint

Use const to create the variable and assign the exact string.

2
Parse the file path into parts
Import the path module and create a variable called parsedPath that stores the result of path.parse(filePath).
Node.js
Hint

Use require('path') to import the module and path.parse(filePath) to parse.

3
Change the file name in the parsed path
Change the base property of parsedPath to "summary.txt".
Node.js
Hint

Assign the new file name string to parsedPath.base.

4
Rebuild the file path string
Create a variable called newFilePath and set it to the result of path.format(parsedPath).
Node.js
Hint

Use path.format with the modified parsedPath to rebuild the path string.

Practice

(1/5)
1. What does path.parse do in Node.js?
easy
A. It breaks a file path into parts like root, dir, base, name, and ext.
B. It combines multiple file paths into one string.
C. It reads the contents of a file at the given path.
D. It deletes a file at the specified path.

Solution

  1. Step 1: Understand the purpose of path.parse

    path.parse takes a file path string and splits it into an object with properties like root, dir, base, name, and ext.
  2. Step 2: Compare with other options

    Options A, C, and D describe different file system operations, not path parsing.
  3. Final Answer:

    It breaks a file path into parts like root, dir, base, name, and ext. -> Option A
  4. Quick Check:

    path.parse splits path into parts [OK]
Hint: Remember: parse means split path into pieces [OK]
Common Mistakes:
  • Confusing path.parse with reading file contents
  • Thinking path.parse combines paths
  • Mixing up path.parse with deleting files
2. Which of the following is the correct way to use path.format to build a path from parts?
easy
A. path.format('file.txt')
B. path.format('/home/user/file.txt')
C. path.format({ root: '/', dir: '/home/user', base: 'file.txt' })
D. path.format(['home', 'user', 'file.txt'])

Solution

  1. Step 1: Identify correct argument type for path.format

    path.format expects an object with path parts like root, dir, base, name, or ext.
  2. Step 2: Check each option

    path.format({ root: '/', dir: '/home/user', base: 'file.txt' }) correctly passes an object with root, dir, and base. Options B, C, and D pass strings or arrays, which are invalid.
  3. Final Answer:

    path.format({ root: '/', dir: '/home/user', base: 'file.txt' }) -> Option C
  4. Quick Check:

    path.format needs object with parts [OK]
Hint: path.format needs an object, not a string or array [OK]
Common Mistakes:
  • Passing a string instead of an object to path.format
  • Using an array instead of an object
  • Confusing path.format with path.parse usage
3. What is the output of this code?
const path = require('path');
const parsed = path.parse('/home/user/docs/file.txt');
console.log(parsed.base);
medium
A. '/home/user/docs/file.txt'
B. 'file.txt'
C. 'file'
D. '.txt'

Solution

  1. Step 1: Understand what path.parse returns

    path.parse returns an object with properties including base, which is the last part of the path with extension.
  2. Step 2: Check the base property for given path

    For '/home/user/docs/file.txt', base is 'file.txt'.
  3. Final Answer:

    'file.txt' -> Option B
  4. Quick Check:

    parsed.base = 'file.txt' [OK]
Hint: base is filename with extension from path.parse [OK]
Common Mistakes:
  • Confusing base with dir or name
  • Expecting full path instead of base
  • Mixing base with extension only
4. Identify the error in this code snippet:
const path = require('path');
const parts = path.parse('/var/log/sys.log');
const newPath = path.format(parts.dir + '/backup/' + parts.base);
console.log(newPath);
medium
A. path.format expects an object, but a string was passed.
B. path.parse cannot parse absolute paths.
C. The variable parts is not defined.
D. The console.log statement is missing parentheses.

Solution

  1. Step 1: Check the argument passed to path.format

    path.format requires an object with path parts, but here a string is passed by concatenating parts.dir, '/backup/', and parts.base.
  2. Step 2: Understand correct usage of path.format

    To add '/backup/' folder, modify parts.dir property or create a new object, then pass that object to path.format.
  3. Final Answer:

    path.format expects an object, but a string was passed. -> Option A
  4. Quick Check:

    path.format needs object, not string [OK]
Hint: path.format always needs an object, never a string [OK]
Common Mistakes:
  • Passing a string instead of an object to path.format
  • Assuming path.parse fails on absolute paths
  • Forgetting parentheses in console.log (not true here)
5. Given this code, what will console.log(newPath) output?
const path = require('path');
const parts = path.parse('/usr/local/bin/node');
const updatedParts = { ...parts, dir: parts.dir + '/backup' };
const newPath = path.format(updatedParts);
console.log(newPath);
hard
A. '/usr/local/bin/backup/'
B. '/usr/local/bin/node/backup'
C. '/usr/local/bin/node'
D. '/usr/local/bin/backup/node'

Solution

  1. Step 1: Analyze how updatedParts modifies dir

    updatedParts copies all parts but changes dir to parts.dir + '/backup', so dir becomes '/usr/local/bin/backup'.
  2. Step 2: Understand path.format output

    path.format builds path from updatedParts, combining dir and base ('node'), resulting in '/usr/local/bin/backup/node'.
  3. Final Answer:

    '/usr/local/bin/backup/node' -> Option D
  4. Quick Check:

    Modified dir + base = '/usr/local/bin/backup/node' [OK]
Hint: Changing dir in parts changes folder path in output [OK]
Common Mistakes:
  • Appending backup to base instead of dir
  • Confusing order of path parts
  • Forgetting to spread parts before modifying