Files
NapCatQQ/.pnpm-store/v3/files/f9/e6b6fe6c64f1fccd220d702f94c20de50b46d531eb53014e6a2387e279c128ac5e9d46f8b3531c045e9f355fe001861e561a57d597a1187b15d404073ab682
TanTan e311ca3275
Build NapCat Artifacts / Windows Loader Test (push) Canceled after 0s
Build NapCat Artifacts / Type Check & Test (push) Canceled after 0s
Build NapCat Artifacts / Build NapCat.Framework (push) Canceled after 0s
Build NapCat Artifacts / Build NapCat.Shell (push) Canceled after 0s
docs: 仓库链接指向本镜像仓库
2026-11-13 09:25:58 +08:00

37 lines
705 B
Plaintext

# import/no-named-default
<!-- end auto-generated rule header -->
Reports use of a default export as a locally named import.
Rationale: the syntax exists to import default exports expressively, let's use it.
Note that type imports, as used by [Flow], are always ignored.
[Flow]: https://flow.org/
## Rule Details
Given:
```js
// foo.js
export default 'foo';
export const bar = 'baz';
```
...these would be valid:
```js
import foo from './foo.js';
import foo, { bar } from './foo.js';
```
...and these would be reported:
```js
// message: Using exported name 'bar' as identifier for default export.
import { default as foo } from './foo.js';
import { default as foo, bar } from './foo.js';
```