path.resolve for absolute paths in Node.js - Cheat Sheet & Quick Revision

Recall & Review

beginner

What does path.resolve() do in Node.js?

path.resolve() creates an absolute path by combining given path segments. It starts from the right and works left until it finds an absolute path or the root.

beginner

How does path.resolve() handle relative paths?

If no absolute path is found in the arguments, path.resolve() uses the current working directory as the base to create an absolute path.

intermediate

What is the difference between path.resolve() and path.join()?

path.resolve() returns an absolute path, resolving '..' and '.' segments and starting from the root or current directory. path.join() just concatenates paths and normalizes them but may return a relative path.

intermediate

Example: What is the output of path.resolve('foo', '/bar', 'baz')?

The output is /bar/baz. Because /bar is an absolute path, path.resolve() ignores foo and starts from /bar.

beginner

Why is path.resolve() useful in Node.js projects?

It helps create absolute paths safely, avoiding errors from relative paths. This is important when working with files or modules to ensure paths are correct regardless of where the script runs.

What does path.resolve() return if no absolute path is given in arguments?

A An absolute path based on current working directory

B A relative path concatenated from arguments

C An error

D The first argument unchanged

If no absolute path is found, path.resolve() uses the current working directory as the base to return an absolute path.

Which method returns an absolute path in Node.js?

A console.log()

B path.join()

C fs.readFile()

D path.resolve()

path.resolve() returns an absolute path, while path.join() may return a relative path.

Given path.resolve('a', 'b', '/c'), what is the output?

A /a/b/c

B /c

C a/b/c

D a/b

The absolute path /c causes path.resolve() to ignore previous segments.

What does path.resolve() do with '.' and '..' in paths?

A Leaves them as is

B Removes all dots

C Resolves and normalizes them

D Throws an error

path.resolve() processes '.' and '..' to simplify the path.

Why prefer path.resolve() over manual string concatenation for paths?

A It handles different OS path formats and normalizes paths

B It runs faster

C It encrypts paths

D It only works on Windows

path.resolve() ensures paths are correct across operating systems and normalizes them.

Explain how path.resolve() creates an absolute path from given segments.

Think about how it builds the path step by step.

Describe the difference between path.resolve() and path.join() in Node.js.

Focus on the output type and path processing.

Practice

1. What does path.resolve do in Node.js?

easy

A. It creates an absolute path from given path segments.

B. It reads the content of a file at a given path.

C. It deletes a file at a specified path.

D. It lists all files in a directory.

Solution

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

   path.resolve combines path segments into a full absolute path.

2. Step 2: Compare with other options

   Reading, deleting, or listing files are unrelated to path.resolve's function.

3. Final Answer:

   It creates an absolute path from given path segments. -> Option A

4. Quick Check:

   path.resolve = absolute path creation [OK]

Hint: Remember: resolve means make full absolute path [OK]

Common Mistakes:

• Confusing path.resolve with file reading functions
• Thinking it deletes or lists files
• Assuming it returns relative paths

2. Which of the following is the correct syntax to use path.resolve to combine 'folder' and 'file.txt'?

easy

A. path.resolve('folder' + 'file.txt')

B. path.resolve['folder', 'file.txt']

C. path.resolve('folder', 'file.txt')

D. path.resolve('folder\\file.txt')

Solution

1. Step 1: Check correct function call syntax

   path.resolve is called with comma-separated arguments inside parentheses.

2. Step 2: Analyze each option

   path.resolve('folder', 'file.txt') uses correct syntax with separate arguments. path.resolve['folder', 'file.txt'] uses brackets incorrectly. path.resolve('folder' + 'file.txt') concatenates strings before passing to form 'folderfile.txt', which lacks a path separator and produces an incorrect path. path.resolve('folder\\file.txt') passes a single string using backslash as separator, which is incorrect on Unix systems and results in a wrong path.

3. Final Answer:

   path.resolve('folder', 'file.txt') -> Option C

4. Quick Check:

   Use commas inside parentheses for path.resolve [OK]

Hint: Use commas inside parentheses to combine paths [OK]

Common Mistakes:

• Using square brackets instead of parentheses
• Concatenating strings manually before passing
• Using backslash separators in path strings

3. Given the current directory is /home/user, what will path.resolve('docs', 'file.txt') return?

medium

A. /home/docs/file.txt

B. docs/file.txt

C. /docs/file.txt

D. /home/user/docs/file.txt

Solution

1. Step 1: Understand path.resolve behavior with relative paths

   When given relative paths, path.resolve resolves them against the current working directory.

2. Step 2: Combine current directory with given segments

   Current directory is /home/user, so resolving 'docs' and 'file.txt' results in /home/user/docs/file.txt.

3. Final Answer:

   /home/user/docs/file.txt -> Option D

4. Quick Check:

   Relative paths resolve from current directory [OK]

Hint: Relative paths resolve from current directory [OK]

Common Mistakes:

• Assuming path.resolve returns relative paths
• Confusing root directory with current directory
• Ignoring current working directory in resolution

4. What is wrong with this code snippet?

const path = require('path');
const fullPath = path.resolve['folder', 'file.txt'];
console.log(fullPath);

medium

A. Using square brackets instead of parentheses for function call.

B. Missing import of the path module.

C. Incorrect variable name for storing the path.

D. Using console.log instead of return.

Solution

1. Step 1: Identify syntax error in function call

   Function calls require parentheses (), not square brackets [].

2. Step 2: Check other parts of the code

   path module is imported correctly, variable name is valid, and console.log is fine for output.

3. Final Answer:

   Using square brackets instead of parentheses for function call. -> Option A

4. Quick Check:

   Function calls need parentheses () [OK]

Hint: Function calls always use parentheses, not brackets [OK]

Common Mistakes:

• Using brackets [] instead of parentheses ()
• Forgetting to import path module
• Confusing console.log with return

5. You want to get the absolute path to a file named config.json located in a folder settings inside your project root. Your current working directory can vary. Which code correctly ensures the absolute path regardless of where the script runs?

hard

A. path.resolve('settings', 'config.json')

B. path.resolve(__dirname, 'settings', 'config.json')

C. path.resolve(process.cwd(), 'settings/config.json')

D. path.resolve('./settings/config.json')

Solution

1. Step 1: Understand __dirname vs process.cwd()

   __dirname is the directory of the current script file, stable regardless of where the script is run from. process.cwd() is the current working directory, which can change.

2. Step 2: Analyze each option

   path.resolve(__dirname, 'settings', 'config.json') uses __dirname to build absolute path reliably. path.resolve('settings', 'config.json') and D depend on current working directory, which may vary. path.resolve(process.cwd(), 'settings/config.json') uses process.cwd() but with a string containing slash, which works but is less clear and can cause issues on some OS.

3. Final Answer:

   path.resolve(__dirname, 'settings', 'config.json') -> Option B

4. Quick Check:

   Use __dirname for stable absolute paths [OK]

Hint: Use __dirname to build absolute paths reliably [OK]

Common Mistakes:

• Using process.cwd() which can change unexpectedly
• Passing combined strings instead of separate parts
• Assuming relative paths always work