no-named-default

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

Rule DetailsCopy Anchor Link

A default export has its own import spelling. Taking it through the named block, import { default as x } from 'm', is a roundabout way to write import x from 'm'. This rule reports it however default is written (an identifier or the string 'default') and also in a type import (import type x from 'm' is the equivalent).

A re-export, export { default as x } from 'm', is not an import and is not reported.

❌ IncorrectCopy Anchor Link

import { default as config } from './config';
import { 'default' as config2 } from './config';
import type { default as Config } from './config';

✅ CorrectCopy Anchor Link

import config from './config';
import type Config from './config';
export { default as config } from './config';

OptionsCopy Anchor Link

[]

No options.

When Not To Use ItCopy Anchor Link

Never needed; the default import spelling always exists.

Use this rule

npm install -D oxlint-plugin-import-next

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

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