import-js/eslint-plugin-import

no-unused-modules "missingExports" returns false positives

Open

#2,102 opened on May 27, 2021

View on GitHub
 (7 comments) (1 reaction) (0 assignees)JavaScript (1,540 forks)batch import
`exports` supportbughelp wanted

Repository metrics

Stars
 (4,946 stars)
PR merge metrics
 (Avg merge 138d 22h) (3 merged PRs in 30d)

Description

I'd expect both of these cases to count as exports:

module.exports = {} // Should probably not trigger

export * from './someFile' // Should almost definitely not trigger

Contributor guide

Research direction
Look at the 'no unused modules' rule implementation to understand how it detects exports, especially for 'module.exports = {}' and 'export * from' patterns, and identify why it incorrectly flags them as missing exports.
Tech stack
javascriptnodejs
Domain
developer experience
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
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.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
JavaScriptESLint
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60