# require-module-specifiers

📝 Require non-empty specifier list in import and export statements.

💼 This rule is enabled in the following [configs](https://github.com/sindresorhus/eslint-plugin-unicorn#recommended-config): ✅ `recommended`, ☑️ `unopinionated`.

🔧💡 This rule is automatically fixable by the [`--fix` CLI option](https://eslint.org/docs/latest/user-guide/command-line-interface#--fix) and manually fixable by [editor suggestions](https://eslint.org/docs/latest/use/core-concepts#rule-suggestions).

<!-- end auto-generated rule header -->
<!-- Do not manually modify this header. Run: `npm run fix:eslint-docs` -->

Enforce non-empty specifier list in `import` and `export` statements. Use a [side-effect import](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/import#import_a_module_for_its_side_effects_only) if needed, or remove the statement.

A single bare `export {}` is allowed when the file has no runtime import/export declarations. TypeScript uses it to distinguish modules from scripts. This exception ignores explicit type-only imports and exports.

## Examples

```js
// ❌
import {} from 'foo';

// ✅
import 'foo';
```

```js
// ❌
import foo, {} from 'foo';

// ✅
import foo from 'foo';
```

```js
// ❌
export {} from 'foo';

// ✅
import 'foo';
```

```js
// ❌
import 'foo';
export {};

// ✅
import 'foo';
```