Closed jj6990 closed 8 months ago
Does anyone knows why is this issue happening?
node 16.8.0
I will try to reproduce. But so far I haven't seen this error. But I am also on node 18. Not sure if it makes a difference though.
Ditto from me.
I'm on node 18.18.0
I got the error to go away by messing around with pageExtensions inside of next.config.js
like this issue.
pageExtensions: ['page.tsx', 'page.ts', 'page.jsx', 'page.js']
, to next.config.js
RS the server and the error goes away but the app 404s.
We can fix the 404:
./frontend/src/pages/en/index.page.tsx
But that breaks the template entirely and then app router & page router don't seem to work together.
New to NextJS so I'm just taking shots in the dark here and don't fully understand even after reading through the docs.
Appreciate your help so far and in advance!
I figured it out, need to actually set up the token, assumed it was placeholder and not required. Thanks for your work!
https://www.youtube.com/watch?v=a23JvssqrrQ&ab_channel=Strapi
Just a suggestion, an error message/prompt might be helpful for future users.
Thanks guys for your help this actually worked for me as well not sure why in production worked normally and locally it didn't
Thank you all amazing folks. @PrimeTimeTran if you have time, would you like to make a PR for it?
@PaulBratslavsky your wish is my command. lol =).
@PrimeTimeTran you are awesome. Thank you and merged. https://github.com/strapi/nextjs-corporate-starter/pull/96
For me, to resolve this error I also have to set up metadata/ global properties in the admin if you are working on a brand new project. Otherwise, lacking of these data will cause rendering errors.