no-named-as-default

💼 This rule is enabled in the following configs: recommended, typescript.

Rule DetailsCopy Anchor Link

A default import bound to the name of a named export of the same module is reported: after import foo from './m', a reader cannot tell whether foo is the module's default or its named foo.

The rule does not read the other module. The evidence that ./m has a named export foo is this file taking that name from the same module: in the same declaration (import foo, { foo as bar } from './m'), in another import (import { foo as bar } from './m'), or in a re-export (export { foo } from './m'). The default can be spelled import foo or import { default as foo }.

Not reported: a default bound to any other name, the name taken from a different module, and evidence that is only a type (import type { foo }, { type foo }), since a type and a default value sharing a name is a judgment call.

❌ IncorrectCopy Anchor Link

import foo, { foo as namedFoo } from './m';

import { default as bar } from './m';
export { bar } from './m';

✅ CorrectCopy Anchor Link

import foo from './m';
import { bar } from './m';

import foo2, { type foo2 as Foo } from './m';

OptionsCopy Anchor Link

[]

ImplementationCopy Anchor Link

• Source Code
• Test Cases

OWASP FoundationCopy Anchor Link

• Category: A00:2021 - General Security

Use this rule

npm install -D oxlint-plugin-import-next

{  "jsPlugins": ["oxlint-plugin-import-next"],  "rules": {    "import-next/no-named-as-default": "error"  }}

import { defineConfig } from 'vite-plus';export default defineConfig({  lint: {    jsPlugins: ['oxlint-plugin-import-next'],    rules: {      'import-next/no-named-as-default': 'error',    },  },});