exportFromImports

Reports imports that are re-exported and could use export...from syntax instead.

✅ This rule is included in the ts stylistic and stylisticStrict presets.

When re-exporting from a module without otherwise using the imported value, it’s unnecessary to import and then export. It can be done in a single export...from declaration, which is more concise and makes the re-export intent clearer.

Examples

Re-exporting Default Export

❌ Incorrect

import defaultExport from "./foo.js";
export default defaultExport;

✅ Correct

export { default } from "./foo.js";

Re-exporting Named Export

❌ Incorrect

import { named } from "./foo.js";
export { named };

✅ Correct

export { named } from "./foo.js";

Re-exporting Namespace

❌ Incorrect

import * as namespace from "./foo.js";
export { namespace };

✅ Correct

export * as namespace from "./foo.js";

Multiple Re-exports

❌ Incorrect

import defaultExport, { named } from "./foo.js";
export default defaultExport;
export { defaultExport as renamedDefault, named, named as renamedNamed };

✅ Correct

export {
  default,
  default as renamedDefault,
  named,
  named as renamedNamed,
} from "./foo.js";
Error ts(2307)  ― Cannot find module './foo.js' or its corresponding type declarations.

Options

This rule is not configurable.

When Not To Use It

If you prefer the explicit import/export pattern for clarity in your codebase, this rule may not be for you.

Further Reading

• MDN: export statement

Equivalents in Other Linters

• Biome: noExportedImports
• ESLint: unicorn/prefer-export-from