a1c04b0162
Closes NEXT-397 Resolve `metadata` and `generateMetadata()` exports along with head during rendering, this is the easy way for now to collect all the metadata properly. Since we can access segment params and search params only in rendering, so I moved all the resolving logic from loader to render process. <!-- 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 that you're making: --> ## Feature - [x] Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. - [ ] Related issues linked using `fixes #number` - [x] [e2e](https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) tests added - [ ] Documentation added - [ ] Telemetry added. In case of a feature if it's used or not. - [ ] Errors have a helpful link attached, see [`contributing.md`](https://github.com/vercel/next.js/blob/canary/contributing.md) --------- Co-authored-by: Tim Neutkens <tim@timneutkens.nl> |
||
|---|---|---|
| .. | ||
| page.tsx | ||