ce6aa207e9
- 将所有图片路径从绝对路径改为使用 process.env.PUBLIC_URL - 修复 HomePage.tsx 中所有图片引用 - 修复 CoursePage.tsx 中所有图片引用 - 确保图片在 GitHub Pages 上正确加载 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
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.