next.js: Uncaught TypeError: Cannot read properties of undefined (reading 'default') at resolveModuleMetaData

Verify canary release

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

Provide environment information

$ npx --no-install next info

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

warn  - Latest canary version not detected, detected: "13.0.1", newest: "13.0.2-canary.2"

Experimental features used: appDir

What browser are you using? (if relevant)

Chrome (107.0.5304.88) / FireFox (106.0.3)

How are you deploying your application? (if relevant)

next dev

Describe the Bug

Note: Experimental features used: appDir

I have the following project setup (also see repo):

When I yarn dev and navigate to http://localhost:3000/route1, all is fine. Then, when I use the navigation bar to navigate to the other route (route2) I sometimes get the following error:

Uncaught TypeError: Cannot read properties of undefined (reading 'default')
    at resolveModuleMetaData (webpack-internal:///(sc_server)/./node_modules/next/dist/compiled/react-server-dom-webpack/server.browser.js:195:82)
    at serializeModuleReference (webpack-internal:///(sc_server)/./node_modules/next/dist/compiled/react-server-dom-webpack/server.browser.js:1298:50)
    at resolveModelToJSON (webpack-internal:///(sc_server)/./node_modules/next/dist/compiled/react-server-dom-webpack/server.browser.js:1660:40)
    at Array.toJSON (webpack-internal:///(sc_server)/./node_modules/next/dist/compiled/react-server-dom-webpack/server.browser.js:1081:40)
    at stringify (<anonymous>)
    at processModelChunk (webpack-internal:///(sc_server)/./node_modules/next/dist/compiled/react-server-dom-webpack/server.browser.js:163:36)
    at retryTask (webpack-internal:///(sc_server)/./node_modules/next/dist/compiled/react-server-dom-webpack/server.browser.js:1823:50)
    at performWork (webpack-internal:///(sc_server)/./node_modules/next/dist/compiled/react-server-dom-webpack/server.browser.js:1856:33)
    at AsyncLocalStorage.run (node:async_hooks:330:14)
    at eval (webpack-internal:///(sc_server)/./node_modules/next/dist/compiled/react-server-dom-webpack/server.browser.js:1934:55)
resolveErrorDev @ client.js?234c:691
processFullRow @ client.js?234c:756
processBinaryChunk @ client.js?234c:789
progress @ client.js?234c:842

--------------------------------------------------------------------------------------------------------------

react-dom.development.js?160d:21285 The above error occurred in the <ServerRoot> component:
    at ServerRoot (webpack-internal:///./node_modules/next/dist/client/app-index.js:114:11)
    at RSCComponent
    at Root (webpack-internal:///./node_modules/next/dist/client/app-index.js:130:11)

Routing back and forth between route1 and route2 gives me the error 100% of the time

However, one clue:

Note that I have 'use client' on both pages for route1 and route2. When I remove either one of the 'use client' lines of the pages, the app works as expected. Why is this?

Expected Behavior

No error should occur when routing manually using the navigation bar.

Link to reproduction

https://github.com/JustinPraas/next13

To Reproduce

1. Check out specified repo
2. yarn install
3. yarn dev
4. Go to http://localhost:3000/route1 or http://localhost:3000/route2
5. Now navigate to the other route (route1/route2 or vice versa) using the navigation bar
6. Repeat step 5 until the mentioned error comes up in the console and the page stops rendering