import-js/eslint-plugin-import

`import/consistent-type-specifier-style` for exports

Open

#3044 opened on Sep 2, 2024

View on GitHub
 (1 comment) (0 reactions) (0 assignees)JavaScript (4,946 stars) (1,540 forks)batch import
enhancementhelp wanted

Description

Like import/consistent-type-specifier-style, but for exports.

Example:

❌ Invalid with ["error", "prefer-top-level"]

export {Foo, type Bar};

✅ Valid with ["error", "prefer-top-level"]

export type {Bar};
export {Foo};

Contributor guide

Tech stack
javascripttypescript
Domain
toolingdeveloper experience
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.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Familiarity with ESLint rule creationUnderstanding of TypeScript type exports
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
The issue requests a new rule similar to existing `consistent type specifier style` but for exports. Start by examining the existing rule implementation in `src/rules/consistent type specifier style.ts` and its tests. The new rule should enforce consistent style for type exports, e.g., preferring `export type { Bar }` over `export { type Bar }`. Implement the rule following the plugin's patterns, register it, and add test cases covering both `prefer top level` and `prefer inline` options.