Client component with instantsearch ui issue with Server Page Component

[rkanani108]

Verify canary release

• I verified that the issue exists in the latest Next.js canary release

Provide environment information

Next JS: "^13.0.1",

Operating System:
Platform: win32
Arch: x64
Version: Windows 10 Pro
Binaries:
Node: 18.12.0
npm: N/A
Yarn: N/A
pnpm: N/A
Relevant packages:
next: 12.3.0
eslint-config-next: N/A
react: 18.2.0
react-dom: 18.2.0

warn - Latest canary version not detected, detected: "12.3.0", newest: "13.0.2-canary.2".
Please try the latest canary version (npm install next@canary) to confirm the issue still exists before creating a new issue.
Read more - https://nextjs.org/docs/messages/opening-an-issue

What browser are you using? (if relevant)

Chrome

How are you deploying your application? (if relevant)

No response

Describe the Bug

Hi Team,

I have created client component with "instantsearch" library and added it to the page component. It loads the page first time correctly, but when I hit the page second time it shows the blank page and give error in console which image is attached.

Expected Behavior

It should be work on every page hit.

Link to reproduction

https://eample.com/test

To Reproduce

Create the client component with help of "instantsearch" library and add it to the Server Page Component. Hit page once it is working fine but after the second page hit page shows as blank.

[icyJoseph]

Strange that your next info prints 12.3.x 👀

Could you put together a reproduction demo?

[rkanani108]

package.json is as below.

"next": "^13.0.1",
"react": "18.2.0",
"react-dom": "18.2.0",

if run command
next -version
it is 12.3.0

Guide me on this to fix.

[rkanani108]

Hi @icyJoseph

I run production demo without adding instant search library. It seems to be same behavior. demo run first time when I hit second time it shows blank screen.

help me to understand what would be the cause for this behavior.

[icyJoseph]

I think it is a windows related issue, see #42400

[JustinPraas]

Having a similar issue, but with an empty project (2 pages with use client). Also on windows.

#42402

[rkanani108]

Hi @icyJoseph,

I tried on another machine facing same issue. It's not looks like windows issue. In my case client component create issues under the dynamic route.

[icyJoseph]

Mmm could you please try to make a reproduction demo? or Stackblitz link? Like this one https://stackblitz.com/edit/vercel-next-js-1aokay?file=app%2Fnotes%2F[id]%2Ferror.tsx Without a proper reproduction repository it'll be hard to get to the bottom of this

[JustinPraas]

Turns out this is an OS issue. Tested the repo on my linux machine and it works as expected.