Jimmy Lai

I'm currently investigating this issue. ~~Maybe this can unblock you: I have no idea why this happens yet but adding a `useEffect` in the client component made the repro work...

Ok I investigated a bit, so I can confirm that this happens with Node 18 and not Node 16. It does not reproduce on the first hit to the page...

Found the bug, let's hope I can get https://github.com/facebook/react/pull/25645 merged fast!

can you include screenshots? should we keep the Next.js prefix?

@vpontis, what @kdy1 is trying to articulate, I think, is: - some degree of support was added in Turbopack for transpiling nested CSS selectors when the browserlist is specified -...

looked into it, I think one thing that @kdy1 might have overlooked is that the browserlists might not get consumed properly. We're investigating.

@stigmartins1 I investigated your scenario, and I landed a fix that should slightly improve the situation in that specific scenario. Basically what happens is that Next.js will compile the `googleapis`...

FWIW I've had the same issue.

Hi @capJavert, sorry we're still looking into it. Some investigation notes: the Script thing is a red herring and we've managed to repro the issue with and without it in...

Hey folks, next.js team member here. I'm investigating this issue. Would anyone care to share with me privately their projects so I can investigate properly? Or a public repro?