group-exports

💼 This rule is enabled in the following configs: recommended, typescript.

Rule DetailsCopy Anchor Link

Export lists scattered across a file make its public surface hard to see. This rule reports a second export list where one statement would do:

• two local lists, export { a }; export { b };
• two re-export lists from the same module, export { a } from './m'; export { b } from './m';

Type-only lists group separately from value lists: export { a } next to export type { T } is not reported, since merging them takes inline type modifiers, a style choice this rule does not make. Two type-only lists are reported.

Inline declaration exports (export const x = 1), export default, export * from and re-exports from different modules are not lists to merge. CommonJS module.exports assignments are not checked.

❌ IncorrectCopy Anchor Link

export { a };
export { b };

export { c } from './m';
export { d } from './m';

export type { T };
export type { U };

✅ CorrectCopy Anchor Link

export { a, b };
export { c, d } from './m';
export type { T, U };

export { e };
export type { V };

OptionsCopy Anchor Link

[]

No options.

When Not To Use ItCopy Anchor Link

When you prefer each export statement next to the code it exports.

Use this rule

npm install -D oxlint-plugin-import-next

{  "jsPlugins": ["oxlint-plugin-import-next"],  "rules": {    "import-next/group-exports": "error"  }}

import { defineConfig } from 'vite-plus';export default defineConfig({  lint: {    jsPlugins: ['oxlint-plugin-import-next'],    rules: {      'import-next/group-exports': 'error',    },  },});