Files
react-native-devtools-frontend/node_modules/eslint-plugin-import/docs/rules/no-default-export.md
T
Tim van der Lippe fdbd42e2f8 Add eslint-import-plugin to node_modules
Will be used to make sure no default exports are in DevTools.

The PRESUBMIT.py has been updated to skip running the formatting check
if node_modules files are affected, to workaround crbug.com/1068198.

DISABLE_THIRD_PARTY_CHECK=Add plugin to node_modules

Bug: 1068198
Change-Id: I04d4dc813daa01099f21d40edf47aaefcc0b045f
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/2135610
Commit-Queue: Tim van der Lippe <tvanderlippe@chromium.org>
Auto-Submit: Tim van der Lippe <tvanderlippe@chromium.org>
Reviewed-by: Jack Franklin <jacktfranklin@chromium.org>
2020-04-07 14:27:34 +00:00

1.2 KiB

import/no-default-export

Prohibit default exports. Mostly an inverse of prefer-default-export.

Rule Details

The following patterns are considered warnings:

// bad1.js

// There is a default export.
export const foo = 'foo';
const bar = 'bar';
export default 'bar';
// bad2.js

// There is a default export.
const foo = 'foo';
export { foo as default }

The following patterns are not warnings:

// good1.js

// There is only a single module export and it's a named export.
export const foo = 'foo';
// good2.js

// There is more than one named export in the module.
export const foo = 'foo';
export const bar = 'bar';
// good3.js

// There is more than one named export in the module
const foo = 'foo';
const bar = 'bar';
export { foo, bar }
// export-star.js

// Any batch export will disable this rule. The remote module is not inspected.
export * from './other-module'

When Not To Use It

If you don't care if default imports are used, or if you prefer default imports over named imports.