0.26.0

Changed

• Behaviour change: the note on a later render INP didn't time no longer says "people still wait for it". It now
  reads "INP doesn't count it, and what started it can't be told." Nothing ties that render to the interaction but
  when it landed, and on hyperdx it was more than once a live tail's timer or a route change, not the click. The
  render itself is still reported with its count and its time, and a render INP did time is said as before.
• Every render inside the script the screen update waited on is counted there, not only the ones with work in them.
  On kaneo a menu's FrameRequestCallback held 8 renders and the sentence said 4, then set the other 4 apart as
  renders after the handlers, "13 ms of rendering in all across 5 commits".
• A later render is said to force layout only where its script held no other commit. A long animation frame gives
  one forced layout figure per script, and on hyperdx the later render was given its whole task's 12 ms where a
  trace put 1.5 ms of it on that render. Where the script held another commit too, the layout clause is left out.
• A later render whose walk ran out of budget is said by its count alone, "rendering at least 4983 components",
  not "inside DBSearchPageContent". The name was where the walk stopped, not where the render went.
• On a production build a render of 1000 components or more takes the blame without a long task of working time,
  where the working time was the larger part of the interaction. hyperdx re-rendered 3104 components in 38 ms of a
  40 ms click and the sentence said the rest went to waiting and painting. A shadcn/ui Sheet's 59 components and
  excalidraw's 149 stay under the line, and a screen update longer than the working time keeps the verdict.

Sources

• Tagged changelog.
• Commits since v0.25.0.
• Published npm package.