mirror of
https://github.com/react/react-native-devtools-frontend.git
synced 2026-10-06 12:01:40 +08:00
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>
1.4 KiB
1.4 KiB
import/no-named-export
Prohibit named exports. Mostly an inverse of no-default-export.
Rule Details
The following patterns are considered warnings:
// bad1.js
// There is only a single module export and it's a named export.
export const foo = 'foo';
// bad2.js
// There is more than one named export in the module.
export const foo = 'foo';
export const bar = 'bar';
// bad3.js
// There is more than one named export in the module.
const foo = 'foo';
const bar = 'bar';
export { foo, bar }
// bad4.js
// There is more than one named export in the module.
export * from './other-module'
// bad5.js
// There is a default and a named export.
export const foo = 'foo';
const bar = 'bar';
export default 'bar';
The following patterns are not warnings:
// good1.js
// There is only a single module export and it's a default export.
export default 'bar';
// good2.js
// There is only a single module export and it's a default export.
const foo = 'foo';
export { foo as default }
// good3.js
// There is only a single module export and it's a default export.
export default from './other-module';
When Not To Use It
If you don't care if named imports are used, or if you prefer named imports over default imports.