df378d33ef
Some checks failed
CI / go (push) Waiting to run
CI / docker (push) Waiting to run
CI / lint-go (push) Waiting to run
CI / lint-docs (push) Waiting to run
CI / check-paperclip (push) Waiting to run
Deploy static site / Deploy to GitHub Pages (push) Has been cancelled
Deploy static site / Deploy via Docker to hatch.surf (push) Has been cancelled
Resolved conflicts by taking GitHub versions for: - .dockerignore, .gitignore, Dockerfile, README.md, docker-compose.yml Kept deploy.sh updated to: - Pull from GitHub (primary source) - Push to Gitea (push-mirror) - Build from site/ directory (GitHub structure) Co-Authored-By: Paperclip <noreply@paperclip.ing>
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.