#Is there a way to build nextjs bundles
1 messages · Page 1 of 1 (latest)
It looks like this may be the default for the /app router? (I'm still learning the ins and outs of that - this is not the case. But the rules for when it renders to the static output in /app router are FAR less clear than they are with /pages router. I kind of wish this was explicit - that I could just define how I want these things rendered using a common vernacular - or at least next would tell me which method is being used. It seems to drive static generation off of detected API use around fetch, which is cool, but also kind of opaque.)
Also, I wonder whether I could actually make this work in the /pages router by using a wild card optional route [[...slugs]] - but that kind of defeats the point of a router.
What's really needed it seems, is a way to set fallback: "blocking" on individual routes? I don't think dynamic routes that have fallback blocking set, with an empty paths array, are rendered during build.
I'm guessing there is just no way to do this?