8 commits

Author	SHA1	Message	Date
Shu Ding	5ddee4494b	Add new target for middleware (#30299) ... Co-authored-by: Jiachi Liu <inbox@huozhi.im> Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com> Co-authored-by: Tim Neutkens <timneutkens@me.com>	2021-10-26 18:50:56 +02:00
Javi Velasco	a815ba9f79	Implement Middleware RFC (#30081) ... This PR adds support for [Middleware as per RFC ](https://github.com/vercel/next.js/discussions/29750). ## 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	2021-10-20 17:52:11 +00:00
Tim Neutkens	7e370134fb	Use import() to load next.config.js (#29935) ... Co-authored-by: JJ Kasper <jj@jjsweb.site> Co-authored-by: Steven <steven@ceriously.com>	2021-10-16 14:22:42 +02:00
JJ Kasper	24b09ad4f8	Add entrypoint tracing (#25538) ... This adds tracing entrypoints directly after they have have been transpiled to allow us to trace before the webpack runtime has been added to the modules. This should allow for more accurate tracing of entrypoints and allow the trace step to be cached. ## Bug - [x] Related issues linked using `fixes #number` - [x] Integration tests added x-ref: https://github.com/vercel/next.js/issues/24700 x-ref: https://github.com/vercel/next.js/issues/26200 x-ref: https://github.com/vercel/next.js/issues/23894 x-ref: https://github.com/vercel/next.js/issues/25431	2021-08-16 19:29:11 +00:00
Tim Neutkens	eddf2054c2	Bypass webpack compilation for precompiled @next/polyfills-nomodule (#27596) ... Removes the extra webpack handling that was previously done, this ensures the file which is already minified and compiled does not get passed through minification again. Largely based on #21418 Closes #21418 The polyfill loading already has tests so no other changes are necessary. ## 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	2021-08-13 22:40:45 +00:00
Gerald Monaco	08a24780b0	Clean up Document in preparation for streaming (#28032) ... We generate the HTML for a document in two steps: First, we generate the body (i.e. everything under `<div id="__next">`). Then we generate the rest of the document and embed the body in it. This doesn't work when the body is a stream, because React can't render the body for us unless we buffer it, and buffering it means not streaming. This PR takes the existing approach for AMP and uses it for all scenarios: instead of rendering HTML, we just render a placeholder that we can replace with HTML later. This will be used in a follow-up PR to let us know where to concatenate the body stream. I also used the opportunity to split out `HtmlContext` from `DocumentProps`, as these will not be the same thing with functional document components.	2021-08-13 03:36:54 +00:00
Jiachi Liu	c51598268a	Leverage blocked page for _error (#26748) ... ## Enhance simplify detection for visiting `_error` x-ref: #26610	2021-07-01 00:08:36 +00:00
Tim Neutkens	136b754396	Move code shared between server/client to "shared" folder (#26734)	2021-06-30 11:43:31 +02:00

Renamed from packages/next/next-server/lib/constants.ts (Browse further)