import-js/eslint-plugin-import

import/named does not report non-existent exports in yarn workspace

Open

#2,005 opened on Mar 12, 2021

View on GitHubContributor guide
 (6 comments) (1 reaction) (0 assignees)JavaScript (1,548 forks)batch import
bughelp wanted

Repository metrics

Stars
 (5,940 stars)
PR merge metrics
 (PR metrics pending)

Description

Screen Shot 2021-03-12 at 9 45 07 AM

https://github.com/jd2rogers2/eslint-plugin-import-bug-minimal-repo for testing it for yourself

as seen above, no report for import/named despite not having an helloFooV2 export from foo/index.js foo and bar are both separate workspaces, bar lists foo as a dependency, and foo is in node_modules
i would expect it to report maybe a larger issue as there is also https://github.com/benmosher/eslint-plugin-import/issues/1832

Contributor guide

Research direction
Reproduce the bug in a minimal yarn workspace setup and inspect how eslint plugin import resolves exports in workspaces.
Tech stack
javascript
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.
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.
Clear
Prerequisites
yarnESLint
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40