import-js/eslint-plugin-import

[feature] make `context.getCwd()` available in resolver

Open

#2108 opened on May 29, 2021

View on GitHub
 (7 comments) (0 reactions) (0 assignees)JavaScript (4,946 stars) (1,540 forks)batch import
enhancementhelp wantedresolver

Description

context: https://github.com/alexgorbatchev/eslint-import-resolver-typescript/issues/74#issuecomment-850754909

process.cwd() could be incorrect, context.getCwd() is the replacement.

Contributor guide

Tech stack
javascripttypescriptnodejs
Domain
toolingdeveloper experience
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.
half day
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.
mostly clear
Prerequisites
Understanding of ESLint plugin resolversFamiliarity with resolver context API
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
The issue requests exposing `context.getCwd()` in the resolver, as discussed in eslint import resolver typescript issue #74. Currently, `process.cwd()` is used, which may be incorrect. To implement, locate the resolver files in the eslint plugin import repository (likely under `src/resolvers/` or similar) and replace `process.cwd()` calls with `context.getCwd()`. Ensure backward compatibility by checking if `context.getCwd` exists. The PR should also update relevant tests and documentation.