import-js/eslint-plugin-import

(group-exports) Option to never put the export next to the declaration

Open

#1,871 opened on Aug 7, 2020

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

Repository metrics

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

Description

I'd like to see an option for always having named exports be specified separately to their definition. e.g.

Fail

export const foo = 'bar';

Pass

const foo = 'bar';

export { foo };

I'm basically trying to mitigate the workflow of moving the export keyword to the bottom of the file if another named export is added.

Contributor guide

Research direction
Implement a new option 'group exports' (or similar) in the relevant ESLint rule to enforce separate export statements. Study existing rule structure and add option logic.
Tech stack
javascript
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.
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
JavaScriptESLint
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65