import-js/eslint-plugin-import

`export import X = Y` seems not being recognized and may trigger `import/namespace` false-positives

Open

#2,935 opened on Dec 8, 2023

View on GitHub
 (7 comments) (0 reactions) (0 assignees)JavaScript (1,540 forks)batch import
bugenhancementhelp wantedtypescript

Repository metrics

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

Description

Reproduction repo: https://github.com/chenxinyanc/eslint-import-uuid-test

Reproduction code

bar.ts

export const test = 123;

buzz.ts

import * as Bar from "./bar";

export import barTest = Bar.test;

index.ts

import * as Buzz from './buzz';  // No exported names found in module './buzz'. (eslint: import/namespace)

console.log(Buzz);

image

Packages

"devDependencies": {
  "@types/uuid": "^9.0.7",
  "@typescript-eslint/eslint-plugin": "^6.9.1",
  "@typescript-eslint/parser": "^6.9.1",
  "eslint": "^8.55.0",
  "eslint-plugin-import": "^2.29.0",
  "tsc": "^2.0.4",
  "typescript": "^5.3.3"
},

Contributor guide

Research direction
Investigate how the 'export import' syntax is handled in the plugin's TypeScript resolver and ensure the namespace rule correctly recognizes the exported names.
Tech stack
typescriptjavascript
Domain
backend
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
TypeScriptESLint
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70