Plugin: import-nextRules
no-internal-modules
Forbid importing the submodules of other modules
💼 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 internal-modules.
Options
[
{
"type": "object",
"properties": {
"maxDepth": {
"type": "number",
"minimum": 0,
"default": 1,
"description": "Maximum allowed depth of module imports (0 = only root, 1 = one level deep)"
},
"allow": {
"type": "array",
"items": {
"type": "string"
},
"default": [],
"description": "Glob patterns for paths that are allowed regardless of depth"
},
"forbid": {
"type": "array",
"items": {
"type": "string"
},
"default": [],
"description": "Glob patterns for paths that are explicitly forbidden"
},
"ignorePaths": {
"type": "array",
"items": {
"type": "string"
},
"default": [],
"description": "Glob patterns for paths to ignore completely"
},
"strategy": {
"type": "string",
"enum": [
"error",
"warn",
"autofix",
"suggest"
],
"default": "error",
"description": "How to handle violations: error (report), warn (report), autofix (fix automatically), suggest (provide suggestions)"
}
},
"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-internal-modules": "error" }}import { defineConfig } from 'vite-plus';export default defineConfig({ lint: { jsPlugins: ['oxlint-plugin-import-next'], rules: { 'import-next/no-internal-modules': '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.