import-js/eslint-plugin-import

Test on `@typescript-eslint/parser` v4 and `eslint-import-resolver-typescript` v2

Open

#2203 opened on Aug 23, 2021

View on GitHub
 (0 comments) (0 reactions) (0 assignees)JavaScript (4,946 stars) (1,540 forks)batch import
build-processhelp wantedtypescript

Description

Let's keep testing on v3 and v1, but also test on v4 and v2.

Contributor guide

Tech stack
javascripttypescriptnodejs
Domain
testing
Issue type
test
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
familiarity with ESLint plugin testingbasic CI knowledge
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
90
Research direction
The issue requests adding test coverage for `@typescript eslint/parser` v4 and `eslint import resolver typescript` v2 while keeping existing tests for v3 and v1. Examine the current test infrastructure, likely found in `.github/workflows/ci.yml` or similar, to see how versions are configured. Look for matrix entries or scripts that run tests with specific peer dependency versions. Extend those to include the new versions. Since no assignee or PR exists, this is a straightforward task for a newcomer.