I was updating my project into latest versions and I crossed into following problem:
If I update either @prismicio/next into 1.3.0+ version version or update Next.js from 13.4.3 to 13.4.19 version, getStaticPaths inside subfolder e.g. /project/[slug] won't work locally. I have found latest version, which does not cause any issues and its version 1.2.1 (for prismicio/next).
The funny thing is that, when I manually type address into url for example "localhost:5000/projects/portfolio" it shows the corresponding data from Prismic, but when I am trying to reach the same exact page via from landingPage (home) by pressing button, it just shows 404 page.
I have tried adding some console.logging inside the "getStaticPaths", but nothing is happening there when pressing the button, only when manually writing the path into url it logs something to terminal.
ALSO when building project into production, it generates the path inside "/project/[slug]" as intended and starting project, user is able to go into path via landingPage.
Been kinda stuck on this few days, and have tried to figure it out that whats causing this problem, is it either on Next.js side or something to do with the @prismicio/next library.
As far as I know, Next.js has not changed the way it generates paths for "pages" router on local envinronment?
In development (next dev), getStaticPaths will be called on every request.
I am curious has anyone else crossed following problem, when updating library into (1.3.0+) version as I have tried now pretty much every version from 1.3.0 ==> 1.3.4.