import-js/eslint-plugin-import

New feature - get error at multiple named import

Open

#1,994 opened on Feb 24, 2021

View on GitHub
 (3 comments) (0 reactions) (0 assignees)JavaScript (4,946 stars) (1,540 forks)batch import
help wantedrule proposal

Description

For better code split and tree shake, need this to warn/error

// WANT THIS
// not ok
import { a, b } from 'package'

// ok
import { a } from 'package/a'
import { b } from 'package/b'

but have this (want Inverted(?) group-exports rule)

Screenshot 2021-02-24 at 18 25 53

If possible, with regex, to ignore selected packages (like react, storybook, @types, etc)

Contributor guide

Tech stack
javascriptnodejs
Domain
developer experiencetooling
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.
1-2 days
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.
mostly clear
Prerequisites
Familiarity with ESLint plugin developmentAST traversalNode.jsRegex knowledge
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
45
Research direction
Examine existing rules in eslint plugin import (e.g., src/rules/) to understand the pattern for creating a new rule. Check the 'group exports' rule mentioned in the issue to see if it can be extended. Review issue comments for maintainer feedback. Study AST of import declarations to design the rule logic. Consider adding a configuration option to ignore specific packages.