Export with generateStaticParams also does a check on the folder name of a dynamic route
Unanswered
Masai Lion posted this in #help-forum
Masai LionOP
I am building a NextJS app that is going to be static. For that, in my
articles path I have a dynamic route. Using generateStaticParams I call the backend to retrieve all articles so we know with what values the path param will be used. This seems to work great. However, what I now see when I run npm run build (with all, bun, npm and pnpm) is it also does a call on [id] which is the folder name and thus dynanmic route segment. I do not expect that to happen. Why does that happen, and how can I mitigate that?