Chunk Load Error using dynamic routes ([lang])

[leof240]

Link to the code that reproduces this issue

https://github.com/leof240/chunk_load_error_nextauth-nextintl

To Reproduce

1. build the project
2. deploy on prod server
3. go to a dynamic locale page like http:site/en
4. the page is showing an error on chunk load error

Current vs. Expected behavior

Current:
In development the site is working as expected.
in a production build and production environment, the site is throwing a Chunk Load Error on the page js file behind

the buttons on the page do not work

Expected:
The expected behaviour is to show a page with 2 buttons for signin and sign out. when clicking the signin button, the session is updated and after a page refresh is shown from the layout and the page.
it's also showing the page title translated into different languages for the /en, /fr, / it

Provide environment information

Node 20.1

npm v9.8.1

Which area(s) are affected? (Select all that apply)

Not sure, App Router, Internationalization (i18n), Middleware / Edge (API routes, runtime)

Which stage(s) are affected? (Select all that apply)

Vercel (Deployed), Other (Deployed)

Additional context

the "next" package is updated to canary version ( 24 / 02 / 2024)

cannot reproduce the error on development environment with npm run start

[leof240]

I managed to remove the next-intl library and the error still persists.

it seems it's occurring when a server component has client components within a dynamic route, so not really dependednt on any external libraries.

[Mifaresss]

I had a similar problem. You should add env NEXTAUTH_URL=your_domain
And maybe use .env.local

[leof240]

I had a similar problem. You should add env NEXTAUTH_URL=your_domain And maybe use .env.local

I'm doing that locally for another project, but it doesn't make any difference

[leof240]

I was able to fix the error. It's related to the previous errors on dynamic routs. There was a problem in the encoding url in server.js

The url was all lower case having the encoded square brackets lowercase therefore not properly encoded. (%5b instead of %5B)

I added a replace statement before the url processing. I'll post the code later for awareness

[akhrarovsaid]

@leof240 Hey Leof 👋

Any chance you got that code handy? I'm currently experiencing an almost identical issue except my uri is getting encoded twice around my slug. So, I'm getting %255B instead of %5B... incredibly frustrating.

Using Next v13.5.6.

Appreciate any help!