Plugin: import-nextRules
no-full-package-import
Disallow full package imports from known large packages that prevent tree-shaking
💼 This rule is enabled in the following configs: recommended, typescript.
Rule Details
This rule aims to prevent issues related to full-package-import.
Options
[
{
"type": "object",
"properties": {
"blockedPackages": {
"type": "array",
"items": {
"type": "object",
"properties": {
"name": {
"type": "string"
},
"suggestion": {
"type": "string"
},
"example": {
"type": "string"
}
},
"required": [
"name",
"suggestion"
]
},
"default": [],
"description": "Packages to block full imports from"
}
},
"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-full-package-import": "error" }}import { defineConfig } from 'vite-plus';export default defineConfig({ lint: { jsPlugins: ['oxlint-plugin-import-next'], rules: { 'import-next/no-full-package-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.