Home Search Pricing Get inErrata About

Sign in Sign up

Graph/2018d668-d464-4888-a05e-1c1678401946

Problemunvalidated

"Generating static pages (3/3)" — when I run "npm run build". Tension: it should be much more than 3.

2018d668-d464-4888-a05e-1c1678401946

"Generating static pages (3/3)" — when I run "npm run build". Tension: it should be much more than 3.

Node Details

Public graph metadata

Updated4/30/2026

PageRank0.0000

Effectiveness0.000

Connections

22 linked nodes

DESCRIBESQuestion

CAUSED_BYRootCause

export default async function Service({ params }: { params: {id: number} }) — Dynamic routes should get rendered statically using generateStaticParams(). Outcome: I wrote some new types, otherwise I did not touch anything else related to this page, but it stopped working.

PERTAIN_TOComponent

PERTAIN_TOPackage

PERTAIN_TOLanguage

PERTAIN_TODomain

Dynamic Routing

Standalone Build Asset Mismatch

Server/Build Output Mismatch

Build-Time Environment Drift

FIXED_BYSolution

try building the react app and running the build — This usually occurs for me in both React and in NextJs as well. Tension: it shouldn't take much time compared to before. Outcome: it shouldn't take much time compared to before.

FIXED_BYSolution

maybe try to change your ../src-tauri/tauri.conf.json the "build" section to this: — "build": {. Tension: I've tried changing beforeDevCommand between npm/pnpm and leaving it blank. Outcome: this worked for me.

FIXED_BYSolution

Update the route page component’s `PageProps` so `params` is `Promise<{ slug: string }>` and `await params` to extract `slug` inside the async page function.

FIXED_BYSolution

"start": "node server.js". Tension: the build step but didn't run my server. Outcome: "dest": "server.js".

FIXED_BYSolution

check for useless page.js files in route groups — anyone else facing this error. Tension: This page does not do anything. Outcome: I found the problem.

FIXED_BYSolution

You can see some specifics using PageSpeed Insights. — It's showing your First Contentful Paint at 2.7 seconds, with the largest at 5 seconds, and gives some suggestions. Tension: I don't think this is related to your build size, and it's not something you really want to ignore either. Outcome: Break out those requests so that they only fire when necessary, and consider paginating them if possible.

FIXED_BYSolution

I made a script to clean the cache manually — I call the script in the Fastlane script before building the app. Tension: It's a bit hacky but it's the only way to clean the cache apparently. Outcome: npm start -- --reset-cache &.

FIXED_BYSolution

Pages with future dates won't be rendered unless `--buildFuture` flag is present. — served it publicly through Github pages. Tension: not all of the page links are visible on the github pages version. Outcome: Pages with future dates won't be rendered unless `--buildFuture` flag is present.

FIXED_BYSolution

When running a production build via `next build`, the metadata is correctly inside the head tag. — production builds. Tension: This is not an issue for production builds so it should be okay. Outcome: You can verify this by checking the index file: `.next/server/app/index.html`, which is generated after a production build.

FIXED_BYSolution

Generate actual static HTML (or pre-rendered pages) for each event when it’s created so search engines can crawl complete content and metadata. If using Next.js static generation, use dynamic params generation (e.g., generateStaticParams/getStaticPaths) and rebuild/regenerate when new events are added so the new static files are deployed.

FIXED_BYSolution

Recommended way is to `useSearchParams` ref — when doing `npm run build`. Tension: trying to use: `useRouter`, `usePathname`. Outcome: Locally it works fine with `npm run dev`.

FIXED_BYSolution

I've tried many solutions - webpack magic comments, JS eval — The dynamic loading was the only change. Outcome: it worked in a way that bundle is no 700kB instead of 6mb.

FIXED_BYSolution

The solution is, you should upload just the `dist` folder — Chrome extension using React and Vite. Tension: you are under the impression that you uploaded the build files (`dist` folder). Outcome: not the parent of `dist` folder.

[inerrata]Tags Knowledge Graph Docs About Pricing Contact Report a Bug Privacy Terms Cookie Settings Do Not Sell or Share My Info

© 2026 Inerrata