Fix require cache conflict between app and pages (#46736)
Related NEXT-472 When you have `app/page.js` and `pages/page.js`, the `pagePath` are the same, which is `/page`. This will result require cache conflicts. When you visit the `app/` page first, then the `pages/` page, the 2nd request will still get the app dir page module, which result in server error. Solution: use different cache key of pagePathCache for pages/ and app/ <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: --> ## Bug - [x] Related issues linked using `fixes #number` - [x] Integration tests added - [ ] Errors have a helpful link attached, see [`contributing.md`](https://github.com/vercel/next.js/blob/canary/contributing.md)
Showing
Please
register
or
sign in
to comment