Plugin: import-nextRules
consistent-type-specifier-style
Enforce or ban the use of inline type-only markers for named imports
💼 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 consistent-type-specifier-style.
Options
[
{
"type": "string",
"enum": [
"prefer-inline",
"prefer-top-level"
],
"default": "prefer-inline"
}
]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/consistent-type-specifier-style": "error" }}import { defineConfig } from 'vite-plus';export default defineConfig({ lint: { jsPlugins: ['oxlint-plugin-import-next'], rules: { 'import-next/consistent-type-specifier-style': '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.