next/script decides when a <script> element gets created; once it exists, the browser's normal rules apply. Measured on Next.js 16.4.5 (next build && next start; --webpack matched) in Chrome 156 and Firefox 159, with a 300 ms beforeInteractive script and a slow image holding load back:
beforeInteractive: the server HTML has a<link rel="preload" as="script">and an inlineself.__next_s.push([src]). Next's bootstrap appends these scripts to<head>one by one, waiting for eachload, and only then hydrates. It ran at 342 ms, afterDOMContentLoaded(153 ms); hydration followed at 388 ms. The docs say it doesn't block hydration, but a 1.5 s script pushed hydration to 1,651 ms.afterInteractive(default): a preload hint from the server; the element is appended to<body>by the component's effect just after hydration (390 ms). It ran at 391 ms, beforeloadat 850 ms, only because the image was still loading.lazyOnload: no hint; appended afterload, insiderequestIdleCallback(854 ms).worker: experimental, and per the docs not supported in the App Router. WithnextScriptWorkerson and Partytown installed, the script was never requested.
By comparison, React wrote plain <script async> and <script defer> straight into the HTML, and both ran at 153 ms, ahead of every strategy.
Two more rules. onLoad, onReady and onError are functions, so only a Client Component can pass them: from a Server Component the build failed with "Event handlers cannot be passed to Client Component props". And scripts are deduplicated per document by id, else src: the same src rendered twice made one element, and navigating away and back didn't run it again. Inline scripts have no src, so they need an id.