nextjs - 💡(How to fix) Fix Bug with Parallel Routes and Params [1 comments, 2 participants]

Link to the code that reproduces this issue

]]

To Reproduce

Shown in the below screenshot, I am trying to make a Layout that has a {header} and a {sidebar}. I want to reuse this layout in different areas of my site but I want to swap out the sidebar for different areas.

I also want a Page to ideally control what goes in the header section, but didn't find a good way to do that so I resorted to setting up the same parallel route slot for the header.

The below code works as in my pages load up... See below for issue and expected behaviour.

Current vs. Expected behavior

My code setup allows me to navigate to any of the sub pages directly and have the header / sidebar update as I change page, but the layout be controlled in 1 file.

As you can see, I have an [assetId] for the main pages, but in an attempt to catch-all for the sidebar I created a [...assetId].

Given the documentation, I would expect the below

Page

const resolvedParams = await params;
//      ^?  === { assetId: string }

Sidebar [...assetId]

const resolvedParams = await params;
//      ^?  === [ assetId, pathPart ]

In both instances they are coming back as an object.

Note: I tried my setup using a default.tsx for the sidebar, but it doesn't change to the default when I deep link into the page.

Provide environment information

Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 11 Pro
  Available memory (MB): 32679
  Available CPU cores: 32
Binaries:
  Node: 22.20.0
  npm: 10.9.3
  Yarn: N/A
  pnpm: 10.18.3
Relevant Packages:
  next: 15.5.4 // There is a newer version (15.5.6) available, upgrade recommended! 
  eslint-config-next: 15.5.4
  react: 19.2.0
  react-dom: 19.2.0
  typescript: 5.8.3
Next.js Config:
  output: N/A

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

Parallel & Intercepting Routes

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

next dev (local)

Additional context

I am not sure if this is the correct way to build what I want, so providing the below as an example

I don't want to load in data in the sidebar / header if the content is the same ideally for page speed, so through parallel routes was the win here