import-js/eslint-plugin-import

Enhance parser to understand TS's `declare module`

Open

#3186 opened on May 15, 2025

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

Description

I was asked to open this issue here, instead of in eslint-import-resolver-typescript

After upgrading from eslint-import-resolver-typescript version 3.8.3 to 4.3.4 and I am getting errors that there are pretty much no exports availaboe from @uidotdev/usehooks.

The breaking change seems to be with version 3.9.0, when there was a migration between resolvers.

Here is a repository that shows the issue: https://github.com/Brandon-Ritchie/eslint-import-reproduction

Contributor guide

Tech stack
typescriptjavascript
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.
active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
TypeScript module systemESLint plugin development
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
Investigate how eslint plugin import resolves exports, focusing on TypeScript declaration files. Look at the current parser code in the repository, especially files related to TypeScript parsing and module resolution. Check the linked reproduction repository to understand the expected behavior. Examine the resolver migration mentioned between versions 3.8.3 and 3.9.0 to identify the breaking change. The goal is to enhance the parser to correctly handle `declare module` statements in `.d.ts` files.