path.resolve for absolute paths in Node.js - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

What is the output of path.resolve with relative and absolute paths?

Consider the following Node.js code using path.resolve. What will be printed?

Node.js

import path from 'path';
console.log(path.resolve('/foo', './bar', 'baz'));

A "/foo/./bar/baz"

B "/foo/bar/baz"

C "/foo/bar/./baz"

D "foo/bar/baz"

💡 Hint

Remember that path.resolve normalizes and joins paths, resolving '.' and '..' segments.

The path.resolve method joins the paths and normalizes them. The ./bar means 'bar' inside the current directory, so it becomes 'bar'. The final path is /foo/bar/baz.

❓ Predict Output

intermediate

What does path.resolve return when given an absolute path last?

What will this code output?

Node.js

import path from 'path';
console.log(path.resolve('foo', '/bar', 'baz'));

A "foo//bar/baz"

B "foo/bar/baz"

C "/foo/bar/baz"

D "/bar/baz"

💡 Hint

When an absolute path appears, path.resolve resets the base to that path.

When path.resolve encounters an absolute path, it discards previous segments and starts from that absolute path. Here, '/bar' is absolute, so the result is '/bar/baz'.

🔧 Debug

advanced

Why does this path.resolve call produce an unexpected path?

This code is intended to resolve to '/home/user/project/src/lib', but it outputs '/home/user/project/lib'. What is the cause?

Node.js

import path from 'path';
const base = '/home/user/project/src';
const result = path.resolve(base, '../lib');
console.log(result);

A Because '../lib' moves one directory up from 'src', so the result is '/home/user/project/lib'.

B Because path.resolve does not normalize '..' segments, so it keeps '../lib' literally.

C Because base should be relative, not absolute, for path.resolve to work correctly.

D Because path.resolve always appends paths without resolving '..' segments.

💡 Hint

Think about what '../lib' means relative to the base path.

The segment '../lib' means go up one directory from 'src' and then into 'lib'. So the resolved path is '/home/user/project/lib'.

❓ component_behavior

advanced

How does path.resolve behave with empty strings in arguments?

What will this code output?

Node.js

import path from 'path';
console.log(path.resolve('', '/foo', '', 'bar'));

A "/foo/bar"

B "foo/bar"

C "/foo//bar"

D "/foo"

💡 Hint

Empty strings are ignored in path.resolve arguments.

Empty strings are skipped. The absolute path '/foo' resets the base, and 'bar' is appended, resulting in '/foo/bar'.

📝 Syntax

expert

Which option causes a SyntaxError when importing and using path.resolve in Node.js ES modules?

Identify the code snippet that will cause a SyntaxError.

A import path from 'path'; console.log(path.resolve('/a', 'b'));

B const path = require('path'); console.log(path.resolve('/a', 'b'));

C import path from 'path'; console.log(path.resolve('/a', 'b')

D import { resolve } from 'path'; console.log(resolve('/a', 'b'));

💡 Hint

Look for missing or extra characters that break syntax.

Option C is missing a closing parenthesis in the console.log call, causing a SyntaxError.