fix: Impl `attachRequestMeta` in base server to handle meta differently in edge…
fix: Impl `attachRequestMeta` in base server to handle meta differently in edge and node servers (#38932) This line was introduced in #38862 to the base server but should only be useful for the Node.js server: ```js addRequestMeta(req, '__NEXT_CLONABLE_BODY', getClonableBody(req.body)) ``` It also introduces polyfill of `stream` to the edge server. Here we add an abstract method to handle it differently, where only `__NEXT_INIT_QUERY` is used. ## Bug - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Errors have helpful link attached, see `contributing.md` ## Feature - [ ] 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` - [ ] Integration tests added - [ ] Documentation added - [ ] Telemetry added. In case of a feature if it's used or not. - [ ] Errors have helpful link attached, see `contributing.md` ## Documentation / Examples - [ ] Make sure the linting passes by running `pnpm lint` - [ ] The examples guidelines are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing.md#adding-examples)
Showing
Please
register
or
sign in
to comment