[Bug]: client-side exception when visiting useLayoutEffect page

Summary

Sometime this afternoon, the page for useLayoutEffect:

https://react.dev/reference/react/useLayoutEffect

broke with:

Application error: a client-side exception has occurred (see the browser console for more information).

Page

https://react.dev/reference/react/useLayoutEffect

Details

Console:

framework-76ad44d61c11f057.js:1 Error: File /src/App.js was defined multiple times. Each file snippet should have a unique path name
    at 145-0963f310eaedf893.js:1:299499
    at Array.reduce (<anonymous>)
    at n (145-0963f310eaedf893.js:1:298499)
    at 145-0963f310eaedf893.js:1:250798
    at lb (framework-76ad44d61c11f057.js:1:41610)
    at aY (framework-76ad44d61c11f057.js:1:61337)
    at aW (framework-76ad44d61c11f057.js:1:60197)
    at aB (framework-76ad44d61c11f057.js:1:59814)
    at ot (framework-76ad44d61c11f057.js:1:76212)
    at ua (framework-76ad44d61c11f057.js:1:111832)
aR @ framework-76ad44d61c11f057.js:1
main-6b2aa10951d4c273.js:1 Error: File /src/App.js was defined multiple times. Each file snippet should have a unique path name
    at 145-0963f310eaedf893.js:1:299499
    at Array.reduce (<anonymous>)
    at n (145-0963f310eaedf893.js:1:298499)
    at 145-0963f310eaedf893.js:1:250798
    at lb (framework-76ad44d61c11f057.js:1:41610)
    at aY (framework-76ad44d61c11f057.js:1:61337)
    at aW (framework-76ad44d61c11f057.js:1:60197)
    at aB (framework-76ad44d61c11f057.js:1:59814)
    at ot (framework-76ad44d61c11f057.js:1:76212)
    at ua (framework-76ad44d61c11f057.js:1:111832)
Q @ main-6b2aa10951d4c273.js:1
main-6b2aa10951d4c273.js:1 A client-side exception has occurred, see here for more info: https://nextjs.org/docs/messages/client-side-exception-occurred
Q @ main-6b2aa10951d4c273.js:1

Browser: Chromium 141, Firefox 143
OS: Linux

Possibly related to 8d73630aa5463c394d1b825d35b804a2a9e4324b (#8058). So, C/C'ing @poteto.

Reproduisez l’exception côté client sur la page de référence de useLayoutEffect dans Chromium ou Firefox et inspectez la console du navigateur pour rechercher l’erreur liée au snippet /src/App.js dupliqué. Comparez la page avec l’issue associée #8058 et identifiez le chemin du snippet dupliqué. C’est terminé lorsque la page se charge sans l’exception côté client et que ses snippets ont des chemins uniques.