import-js/eslint-plugin-import

Type only exports get flagged as not used by import/no-unused-modules

Open

#2,502 opened on Jul 19, 2022

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

Description

I have one file which uses a type export:

export type TopNavStore = {

Which is clearly imported with a type only import in another file:

import { createStore, ZustandProvider, type TopNavStore } from './store';

But it gets flagged with : 35:1 warning exported declaration 'TopNavStore' not used within other modules import/no-unused-modules

The file is a .tsx file from a .ts file if that matters?

Contributor guide

Tech stack
typescriptjavascript
Domain
tooling
Issue type
bug
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
ESLint plugin development basicsTypeScript type importsJavaScript module systems
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65
Research direction
Investigate the import/no unused modules rule implementation in eslint plugin import. The bug likely occurs when checking exports that are type only. Look at how the rule handles TypeScript type exports (e.g., in the rule's logic for collecting exports). Review the issue comments for any additional context. Check the rule's test file for existing tests related to type only exports.