Avoid empty exports that don't change anything

Docs > Code Analysis > Static Analysis Rules > Avoid empty exports that don't change anything

Cette page n'est pas encore disponible en français, sa traduction est en cours.
Si vous avez des questions ou des retours sur notre projet de traduction actuel, n'hésitez pas à nous contacter.

Metadata

ID: typescript-code-style/no-useless-empty-export

Language: TypeScript

Severity: Notice

Category: Best Practices

Description

Do not use empty exports.

Non-Compliant Code Examples

export const value = 'Hello, world!';
export {};

import 'some-other-module';
export {};

Compliant Code Examples

declare module '_';
import {} from '_';
import * as _ from '_';
export = {};
export = 3;
export const _ = {};

const _ = {};
export default _;

export * from '_';
export = {};

How to use this rule

1
2
rulesets:
  - typescript-code-style     # Rules to enforce TypeScript code style.

Create a static-analysis.datadog.yml with the content above at the root of your repository
Use our free IDE Plugins or add Code Analysis scans to your CI pipelines
Get feedback on your code

For more information, please read the Code Analysis documentation

VS Code Extension

Identify code vulnerabilities directly in your
VS Code editor

JetBrains Plugin

Identify code vulnerabilities directly in
JetBrains products