Plugin: import-nextRules
no-named-export
Prevents named exports
💼 This rule is enabled in the following configs: recommended, typescript.
Rule Details
This rule aims to prevent issues related to named-export.
Options
[
{
"type": "object",
"properties": {
"allowInFiles": {
"type": "array",
"items": {
"type": "string"
},
"description": "Allow named exports in specific files."
},
"allowNames": {
"type": "array",
"items": {
"type": "string"
},
"description": "Allow specific named exports."
},
"allowPatterns": {
"type": "array",
"items": {
"type": "string"
},
"description": "Allow named exports for specific patterns."
},
"suggestDefault": {
"type": "boolean",
"default": true,
"description": "Suggest default export alternative."
}
},
"additionalProperties": false
}
]Implementation
OWASP Foundation
- 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-export": "error" }}import { defineConfig } from 'vite-plus';export default defineConfig({ lint: { jsPlugins: ['oxlint-plugin-import-next'], rules: { 'import-next/no-named-export': 'error', }, },});oxlint-plugin-import-next re-exports eslint-plugin-import-next/oxlint: the same rules under the same IDs, and no ESLint install. Why oxlint.
Did this rule catch something? Star the repo to get new CWE coverage as we ship it — or follow the AI-code-security benchmarks behind these rules.