https://github.com/mhart/nextjs-patch-bug

Reproduction for Next.js issue 65381
https://github.com/mhart/nextjs-patch-bug

Last synced: 11 days ago
JSON representation

Reproduction for Next.js issue 65381

• Host: GitHub
• URL: https://github.com/mhart/nextjs-patch-bug
• Owner: mhart
• Created: 2024-05-05T11:09:18.000Z (8 months ago)
• Default Branch: main
• Last Pushed: 2024-05-05T11:15:34.000Z (8 months ago)
• Last Synced: 2024-10-29T21:13:11.415Z (about 2 months ago)
• Language: TypeScript
• Homepage:
• Size: 35.2 KB
• Stars: 0
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# Next.js fetch-patch bug

Reproduction for [Next.js issue 65381](https://github.com/vercel/next.js/issues/65381)

Illustrates the problem with [setting the `__nextPatched` property on the fetch function itself](https://github.com/vercel/next.js/blob/9ec37c120aba9d5f16e00566a10cba68858e363d/packages/next/src/server/lib/patch-fetch.ts#L779) to determine if the function has already been patched.

Any other library / function that patches global fetch will essentially hide this property, and so Next.js will subsequently try to patch it again.

Aside from extra stack overhead, memory usage, recursive trace calls, etc, this might not be a huge problem – but something (not entirely sure what) causes it to deadlock once it's been wrapped multiple times.

## Reproducing

```

npm install

npm run deploy

```

Then load the page (will probably load fine), and then reload the page.

May need to load a few times to ensure you hit the same isolate, but works first reload for me.

Second page load should freeze and eventually 504.

Can be seen live at https://nextjs-bug-eight.vercel.app