Repository: next.js
Issue: Nextjs conflict with next-auth and pusher
Labels: Navigation,Runtime

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
      Platform: win32
      Arch: x64
      Version: Windows 10 Pro
    Binaries:
      Node: 18.14.0
      npm: N/A
      Yarn: N/A
      pnpm: N/A
    Relevant packages:
      next: 13.4.5-canary.7
      eslint-config-next: 13.4.4
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 5.0.4
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

App directory (appDir: true), ESLint (eslint-config-next), Middleware / Edge (API routes, runtime), Package manager (npm, pnpm, Yarn), Routing (next/router, next/navigation, next/link)

### Link to the code that reproduces this issue or a replay of the bug

https://codesandbox.io/p/github/khanhthanhdev/messenger-clone/main?layout=%257B%2522sidebarPanel%2522%253A%2522EXPLORER%2522%252C%2522rootPanelGroup%2522%253A%257B%2522direction%2522%253A%2522horizontal%2522%252C%2522type%2522%253A%2522PANEL_GROUP%2522%252C%2522id%2522%253A%2522ROOT_LAYOUT%2522%252C%2522panels%2522%253A%255B%257B%2522type%2522%253A%2522PANEL_GROUP%2522%252C%2522direction%2522%253A%2522horizontal%2522%252C%2522id%2522%253A%2522EDITOR%2522%252C%2522panels%2522%253A%255B%257B%2522type%2522%253A%2522PANEL%2522%252C%2522panelType%2522%253A%2522TABS%2522%252C%2522id%2522%253A%2522clin4z92q000b3n6mfrar50se%2522%257D%255D%252C%2522sizes%2522%253A%255B100%255D%257D%252C%257B%2522type%2522%253A%2522PANEL_GROUP%2522%252C%2522direction%2522%253A%2522horizontal%2522%252C%2522id%2522%253A%2522DEVTOOLS%2522%252C%2522panels%2522%253A%255B%257B%2522type%2522%253A%2522PANEL%2522%252C%2522panelType%2522%253A%2522TABS%2522%252C%2522id%2522%253A%2522clin4z92q000d3n6mi0z4d0jf%2522%257D%255D%252C%2522sizes%2522%253A%255B100%255D%257D%255D%252C%2522sizes%2522%253A%255B50%252C50%255D%257D%252C%2522tabbedPanels%2522%253A%257B%2522clin4z92q000b3n6mfrar50se%2522%253A%257B%2522tabs%2522%253A%255B%257B%2522id%2522%253A%2522clin4z92q000a3n6mpm98htpl%2522%252C%2522mode%2522%253A%2522permanent%2522%252C%2522type%2522%253A%2522FILE%2522%252C%2522filepath%2522%253A%2522%252FREADME.md%2522%257D%255D%252C%2522id%2522%253A%2522clin4z92q000b3n6mfrar50se%2522%252C%2522activeTabId%2522%253A%2522clin4z92q000a3n6mpm98htpl%2522%257D%252C%2522clin4z92q000d3n6mi0z4d0jf%2522%253A%257B%2522tabs%2522%253A%255B%257B%2522id%2522%253A%2522clin4z92q000c3n6mz57kkmn8%2522%252C%2522mode%2522%253A%2522permanent%2522%252C%2522type%2522%253A%2522PROJECT_SETUP%2522%257D%255D%252C%2522id%2522%253A%2522clin4z92q000d3n6mi0z4d0jf%2522%252C%2522activeTabId%2522%253A%2522clin4z92q000c3n6mz57kkmn8%2522%257D%257D%252C%2522showDevtools%2522%253Atrue%252C%2522showSidebar%2522%253Atrue%252C%2522sidebarPanelSize%2522%253A15%257D

### To Reproduce

<html>
<body>
<!--StartFragment-->

npm WARN While resolving: next-auth@4.22.1
--
19:08:41.767 | npm WARN Found: next@13.4.5-canary.7
19:08:41.767 | npm WARN node_modules/next
19:08:41.767 | npm WARN   next@"^13.4.5-canary.7" from the root project
19:08:41.767 | npm WARN
19:08:41.767 | npm WARN Could not resolve dependency:
19:08:41.767 | npm WARN peer next@"^12.2.5 \|\| ^13" from next-auth@4.22.1
19:08:41.767 | npm WARN node_modules/next-auth
19:08:41.767 | npm WARN   next-auth@"^4.22.1" from the root project
19:08:41.768 | npm WARN   1 more (@next-auth/prisma-adapter)
19:08:41.768 | npm WARN
19:08:41.768 | npm WARN Conflicting peer dependency: next@13.4.4
19:08:41.768 | npm WARN node_modules/next
19:08:41.768 | npm WARN   peer next@"^12.2.5 \|\| ^13" from next-auth@4.22.1
19:08:41.768 | npm WARN   node_modules/next-auth
19:08:41.768 | npm WARN     next-auth@"^4.22.1" from the root project
19:08:41.768 | npm WARN     1 more (@next-auth/prisma-adapter)
19:08:41.772 | npm WARN ERESOLVE overriding peer dependency
19:08:41.772 | npm WARN While resolving: next-cloudinary@4.12.0
19:08:41.772 | npm WARN Found: next@13.4.5-canary.7
19:08:41.773 | npm WARN node_modules/next
19:08:41.773 | npm WARN   next@"^13.4.5-canary.7" from the root project
19:08:41.773 | npm WARN
19:08:41.773 | npm WARN Could not resolve dependency:
19:08:41.773 | npm WARN peer next@"^12 \|\| ^13" from next-cloudinary@4.12.0
19:08:41.773 | npm WARN node_modules/next-cloudinary
19:08:41.773 | npm WARN   next-cloudinary@"^4.4.0" from the root project
19:08:41.773 | npm WARN
19:08:41.773 | npm WARN Conflicting peer dependency: next@13.4.4
19:08:41.773 | npm WARN node_modules/next
19:08:41.773 | npm WARN   peer next@"^12 \|\| ^13" from next-cloudinary@4.12.0
19:08:41.773 | npm WARN   node_modules/next-cloudinary
19:08:41.773 | npm WARN     next-cloudinary@"^4.4.0" from the root project
19:08:41.777 | npm WARN ERESOLVE overriding peer dependency
19:08:41.777 | npm WARN While resolving: next-superjson-plugin@0.5.8
19:08:41.777 | npm WARN Found: next@13.4.5-canary.7
19:08:41.777 | npm WARN node_modules/next
19:08:41.777 | npm WARN   next@"^13.4.5-canary.7" from the root project
19:08:41.777 | npm WARN
19:08:41.777 | npm WARN Could not resolve dependency:
19:08:41.778 | npm WARN peer next@"^13" from next-superjson-plugin@0.5.8
19:08:41.778 | npm WARN node_modules/next-superjson-plugin
19:08:41.778 | npm WARN   next-superjson-plugin@"^0.5.7" from the root project
19:08:41.778 | npm WARN
19:08:41.778 | npm WARN Conflicting peer dependency: next@13.4.4
19:08:41.778 | npm WARN node_modules/next
19:08:41.778 | npm WARN   peer next@"^13" from next-superjson-plugin@0.5.8
19:08:41.778 | npm WARN   node_modules/next-superjson-plugin
19:08:41.779 | npm WARN     next-superjson-plugin@"^0.5.7" from the root project

<!--EndFragment-->
</body>
</html>

### Describe the Bug

Nextjs 13.4 conflict with other libs : next-auth, pusher, superjson

### Expected Behavior

When i run in local:
![image](https://github.com/vercel/next.js/assets/100078354/4f6f9306-952b-450b-9e1b-6a32930b00be)

I want to deploy and use: npm install --force
Although i deploy successfully, the preview is just : hello messenger ( in app/page.tsx)

### Which browser are you using? (if relevant)

Edge

### How are you deploying your application? (if relevant)

Vercel