sindresorhus/resolve-from

From version Node v8.9.0, require.resolve() accepts custom paths

Open

#8 opened on Oct 31, 2017

View on GitHub
 (7 comments) (6 reactions) (0 assignees)JavaScript (145 stars) (14 forks)user submission
enhancementhelp wanted

Description

See the new require.resolve.paths(request) and the updated require.resolve(request[, options]).

resolve-from can use these new exposed functions instead of accessing private functions of Module. Of course, only when they are available.

Contributor guide

Tech stack
javascriptnodejs
Domain
tooling
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Node.js module systemrequire.resolve() API
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70
Research direction
Review the Node.js documentation for require.resolve() and require.resolve.paths(). Examine the current source code of resolve from to identify where private Module functions are used. Implement conditional usage of the new public APIs for Node.js versions >=8.9.0. Consider backward compatibility for older Node versions. Check the comments in the issue for any additional suggestions or constraints.
From version Node v8.9.0, require.resolve() accepts custom paths · sindresorhus/resolve-from#8 | Good First Issue