Plugin: import-nextRules
prefer-direct-import
Prefer direct imports over barrel imports for better tree-shaking and build performance
💼 This rule is enabled in the following configs: recommended, typescript.
🔧 This rule is automatically fixable by the --fix CLI option.
💡 This rule is manually fixable by editor suggestions.
Rule Details
This rule aims to prevent issues related to prefer-direct-import.
Options
[
{
"type": "object",
"properties": {
"mappings": {
"type": "array",
"items": {
"type": "object",
"properties": {
"barrel": {
"type": "string"
},
"directPath": {
"type": "string"
}
},
"required": [
"barrel",
"directPath"
]
},
"default": [],
"description": "Mapping of barrel paths to direct import patterns"
},
"autoFix": {
"type": "boolean",
"default": true,
"description": "Auto-fix the imports when possible"
}
},
"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/prefer-direct-import": "error" }}import { defineConfig } from 'vite-plus';export default defineConfig({ lint: { jsPlugins: ['oxlint-plugin-import-next'], rules: { 'import-next/prefer-direct-import': '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.