flying-hero
96f6318101
新增: - backend/venv/ - Python 虚拟环境 - backend/start.sh - 启动脚本（使用虚拟环境） - backend/requirements.txt - 依赖列表 - .gitignore - 忽略虚拟环境和缓存文件 说明: - 每个项目使用独立虚拟环境 - 避免依赖冲突 - 启动脚本自动创建和激活虚拟环境
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.