{"record":{"id":"8521ac5b30d29a8f","repo":"oxc-project/oxc","slug":"prevent-usage-of-next-script-in-next-head-comp","errorCode":null,"errorMessage":"Prevent usage of `next/script` in `next/head` component.","messagePattern":"Prevent usage of `next/script` in `next/head` component\\.","errorType":"validation","errorClass":"OxcDiagnostic","httpStatus":null,"severity":"warning","filePath":"crates/oxc_linter/src/rules/nextjs/no_script_component_in_head.rs","lineNumber":12,"sourceCode":"use oxc_ast::{\n AstKind,\n ast::{ImportDeclarationSpecifier, JSXChild, JSXElementName},\n};\nuse oxc_diagnostics::OxcDiagnostic;\nuse oxc_macros::declare_oxc_lint;\nuse oxc_span::{GetSpan, Span};\n\nuse crate::{AstNode, context::LintContext, rule::Rule};\n\nfn no_script_component_in_head_diagnostic(span: Span) -> OxcDiagnostic {\n OxcDiagnostic::warn(\"Prevent usage of `next/script` in `next/head` component.\")\n .with_help(\"See https://nextjs.org/docs/messages/no-script-component-in-head\")\n .with_label(span)\n}\n\n#[derive(Debug, Default, Clone)]\npub struct NoScriptComponentInHead;\n\ndeclare_oxc_lint!(\n /// ### What it does\n ///\n /// Prevent usage of `next/script` in `next/head` component.\n ///\n /// ### Why is this bad?\n ///\n /// The `next/script` component should not be used in a `next/head` component.\n /// Instead move the `` component outside of `` instead.\n ///\n /// ### Examples","sourceCodeStart":1,"sourceCodeEnd":30,"githubUrl":"https://github.com/oxc-project/oxc/blob/e1e7af627c8843ab64044ed466b128fcc21a035b/crates/oxc_linter/src/rules/nextjs/no_script_component_in_head.rs#L1-L30","documentation":"Warning from oxlint rule `nextjs/no-script-component-in-head`. `next/script` manages its own injection and loading priority; nesting it inside `next/head`'s `` causes double handling and ordering bugs (classic symptom: the script never runs, or runs twice). The rule reports a `Script` from `next/script` placed anywhere in the subtree of a `Head` from `next/head`.","triggerScenarios":"A `