Plugin: import-nextRules
no-legacy-imports
Detect imports from deprecated internal paths and suggest alternatives
💼 This rule is enabled in the following configs: recommended, typescript.
🔧 This rule is automatically fixable by the --fix CLI option.
Rule Details
This rule aims to prevent issues related to legacy-imports.
Options
[
{
"type": "object",
"properties": {
"mappings": {
"type": "array",
"items": {
"type": "object",
"properties": {
"deprecated": {
"type": "string"
},
"replacement": {
"type": "string"
},
"reason": {
"type": "string"
},
"since": {
"type": "string"
},
"deadline": {
"type": "string"
}
},
"required": [
"deprecated",
"replacement"
]
}
},
"severity": {
"type": "string",
"enum": [
"warn",
"error"
],
"default": "warn"
}
},
"required": [
"mappings"
],
"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-legacy-imports": "error" }}import { defineConfig } from 'vite-plus';export default defineConfig({ lint: { jsPlugins: ['oxlint-plugin-import-next'], rules: { 'import-next/no-legacy-imports': '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.