#NextJS is not able to parse HTML on different routes
1 messages · Page 1 of 1 (latest)
but in the build
Home Page ^^ - this is fine
But when i click on Test this is what i see:
just tried with brand new app, still the same behavior 😦
and i do have the setup in next.config.js:
/** @type {import('next').NextConfig} */
const nextConfig = {
output: 'export',
}
module.exports = nextConfig
both of my screens are server components if that matters somehow
anyone 😭
can you try upgrading to the newly released 1.4 version? (only the rust crates are updated right now, cli is still being published)
it fixed an issue other people had with nextjs maybe yours too
Like I said, the CLI indeed needs more time
But the fix i mentioned was in the rust crate anyway
ahh sorry, yea you are right bro