react-doctor/nextjs-no-vercel-og-import

Replace the @vercel/og import with import { ImageResponse } from "next/og"

Validation prompt

Confirm the detector match and collect the required evidence before deciding whether an edit is warranted.

Fires on any ImportDeclaration whose source string literal is exactly "@vercel/og": the sole predicate is node.source?.value === "@vercel/og", so it matches default, named (ImageResponse), namespace, and side-effect imports alike, regardless of which symbols are pulled in. Because the match is exact equality, the predicate does NOT match a subpath like "@vercel/og/something" or a re-export through a local wrapper module, so those will never be flagged. Real caveat to verify before applying the fix: the detector has no version awareness, so confirm the project is on Next.js 14+: next/og only exists from Next 14.0.0, where ImageResponse moved there from @vercel/og (on 13.3.x–13.x it lives at next/server, and Next < 13.3 must import @vercel/og directly). Suppress if the project is on Next < 14 and genuinely cannot import from next/og.

Evidence boundary

The diagnostic proves only that the detector’s modeled source pattern matched. It does not prove runtime impact, product intent, rendered failure, or that one remediation is correct.

Establish the environment, repository policy, exceptions, and required rendered or runtime evidence before deciding the occurrence.

Record one outcome:

• Confirmed failure: The required evidence establishes the violation.
• Rejected: A documented exception or false-positive predicate applies.
• Needs evidence: Named evidence can still be collected.
• Unavailable: Required evidence cannot be collected in this run.
• Waived with evidence: An authorized, scoped exception applies to an established failure.
• Observation: The review records an optional tradeoff without claiming a defect.

A waiver records its scope, authority, evidence, and review condition. It is not a pass or false positive.

Default severity is registry metadata. Use the occurrence’s JSON severity after repository configuration when ordering real findings.

Fix prompt

Apply this candidate correction only after the required evidence confirms the risk.

Change the import source from "@vercel/og" to "next/og", keeping the same named bindings, e.g. replace import { ImageResponse } from "@vercel/og" with import { ImageResponse } from "next/og"; Next.js bundles @vercel/og, so importing it directly duplicates code and risks a version mismatch between your dependency and the bundled copy. Only do this on Next.js 14+, where next/og exists; on Next 13.3–13.x import ImageResponse from "next/server" instead, and on Next < 13.3 keep the @vercel/og import. https://nextjs.org/docs/app/api-reference/functions/image-response

Repository-wide copy prompt

Use this repository-wide prompt only after validating each occurrence. For one occurrence, use the guidance above.