Plugin: import-nextRules
enforce-dependency-direction
Ensures dependencies flow in the correct architectural direction
💼 This rule is enabled in the following configs: recommended, typescript.
💡 This rule is manually fixable by editor suggestions.
Rule Details
This rule aims to prevent issues related to enforce-dependency-direction.
Options
[
{
"type": "object",
"properties": {
"layers": {
"type": "array",
"items": {
"type": "string"
},
"default": [
"domain",
"application",
"infrastructure",
"presentation"
],
"description": "Layer definitions with dependency order"
},
"layerPatterns": {
"type": "array",
"items": {
"type": "string"
},
"default": [
"domain",
"application",
"infrastructure",
"presentation",
"ui",
"api"
],
"description": "Layer directory patterns"
},
"allowSameLayer": {
"type": "boolean",
"default": true,
"description": "Allow same-layer imports"
}
},
"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/enforce-dependency-direction": "error" }}import { defineConfig } from 'vite-plus';export default defineConfig({ lint: { jsPlugins: ['oxlint-plugin-import-next'], rules: { 'import-next/enforce-dependency-direction': '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.