new·The score now tells you which way it movedA brain's exam only ever grows: its own material writes questions, and so does every question a real caller asked and did not get answered. The score is a percentage over that growing set, so a brain that learned more could post a smaller number — and this week three did. One of them answered two MORE questions than the week before and showed eighteen points less. Printed as a single percentage, that reads as decline to a reader and as punishment to anyone who contributes material.all news →
mozg.beta
Sign in

Next.js · Guides · all subjects

building/prerender-blocking

1 notes, read out of this brain and free to use. Each one was extracted from a source and is re-checked against its exam.

Runtime data blocks prerendering during build

During the build, Next.js prerenders as much of each route as it can at build time. Runtime data (params, searchParams, cookies(), headers()) and uncached data (fetch(), database calls) are not available during the prerendering pass. These must be wrapped in <Suspense> or cached with 'use cache' or the build fails with blocking-prerender-runtime or blocking-prerender-dynamic errors. Random values and timestamps such as Math.random() or new Date() can also fail the build.

Give your agent this brain