typescript/consistent-type-exports Style
What it does
Enforce using export type for exports that are only used as types.
Why is this bad?
Mixing type-only exports with value exports without export type makes module intent harder to read and can cause unnecessary runtime export surface.
Examples
Examples of incorrect code for this rule:
ts
type Foo = { bar: string };
export { Foo };
export { TypeOnly, value } from "./mod";Examples of correct code for this rule:
ts
type Foo = { bar: string };
export type { Foo };
export type { TypeOnly } from "./mod";
export { value } from "./mod";Configuration
This rule accepts a configuration object with the following properties:
fixMixedExportsWithInlineTypeSpecifier
type: boolean
default: false
Enables an autofix strategy that rewrites mixed exports using inline type specifiers.
How to use
To enable this rule using the config file or in the CLI, you can use:
json
{
"options": {
"typeAware": true
},
"rules": {
"typescript/consistent-type-exports": "error"
}
}ts
import { defineConfig } from "oxlint";
export default defineConfig({
options: { typeAware: true },
rules: {
"typescript/consistent-type-exports": "error",
},
});bash
oxlint --type-aware --deny typescript/consistent-type-exportsVersion
This rule was added in v0.0.8.