- 09 Nov, 2023 9 commits
-
-
vercel-release-bot authored
-
Tobias Koppers authored
* https://github.com/vercel/turbo/pull/6399 * https://github.com/vercel/turbo/pull/6393 * https://github.com/vercel/turbo/pull/6403 * https://github.com/vercel/turbo/pull/6404 * https://github.com/vercel/turbo/pull/6394 * https://github.com/vercel/turbo/pull/6405 * https://github.com/vercel/turbo/pull/6351
-
OJ Kwon authored
### What Apply correct url rewrite behavior in the specific context (pages/api). This won't change anything yet, but it will prevent breaking changes when turbopack makes future changes.
-
Rich Haines authored
This PR fixes the terminal link to server actions size limitations for body size limit. The link is wrong and sending people to a 404
-
vercel-release-bot authored
-
Josh Story authored
Updated React from 7508dcd5c to 746890329. - https://github.com/facebook/react/pull/27674
-
Zack Tanner authored
Wraps this test in a `check` since the experimental log seems to occasionally come in late ([x-ref](https://github.com/vercel/next.js/actions/runs/6805954994/job/18506429726#step:27:410))
-
Sebastian Markbåge authored
This phrasing was changed.
-
Zack Tanner authored
Instead of requiring React in `maybePostpone` (which is susceptible to referencing the wrong version of React during build time, such as in the case where the static worker patches fetch within an app-route, which doesn't have an experimental runtime), this provides the postpone API to the `staticGenerationStore`. That way we know the API is available in render which is when we'd expect to postpone.
-
- 08 Nov, 2023 29 commits
-
-
vercel-release-bot authored
-
Sebastian Markbåge authored
The "postpone" terminology is internal to React and can be used for more things than just this. It's also a mechanism we may or may not rely on. --------- Co-authored-by:Zack Tanner <zacktanner@gmail.com>
-
Sebastian Markbåge authored
Other ways such as on the client.
-
Zack Tanner authored
Fixes a broken link, shortens the title, and adds another possible way to resolve the error. Co-authored-by:kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
-
vercel-release-bot authored
-
Josh Story authored
Updated React from 2983249dd to 7508dcd5c. - https://github.com/facebook/react/pull/27672 - https://github.com/facebook/react/pull/27132 - https://github.com/facebook/react/pull/27646 - https://github.com/facebook/react/pull/26446
-
Jimmy Lai authored
This PR fixes the bug in which interception routes of the form `(.)[param]` would not intercept navigations. The bug happened because we would not create a dynamic route matcher for the intercepted route, so we would never match the correct dynamic route when hitting the server, falling back to the base one. The fix consists of fixing the logic that checks for a dynamic route so that it checks the correct path when handling an interception route. There's probably a better fix here, advice welcome fixes #52533
-
Maia Teegarden authored
-
Zack Tanner authored
Follow up to #58203 to skip this in tests to avoid issues once we cut stable
-
Michael Novotny authored
### Description Adds config for experimental PPR support ### Related Issue(s)/Incident Prior art: #57444 ### Best Way to Test Visit → docs/app/api-reference/next-config-js/partial-prerendering Co-authored-by:
Amy Burns <5012825+timeyoutakeit@users.noreply.github.com> Co-authored-by:
Lee Robinson <9113740+leerob@users.noreply.github.com>
-
-
vercel-release-bot authored
-
Zack Tanner authored
Fixes a bug where when `config.experimental.ppr` was set, we didn't show the proper warning indicator that the feature is experimental.
-
Sebastian Markbåge authored
Seems like the default 2000 limit is getting hit. Start more conservative while investigating why. Picked half to start.
-
Zack Tanner authored
This is to ensure that folks experimenting with PPR are receiving the latest updates as the feature is actively being worked on.
-
Asad Khan authored
-
Lee Robinson authored
Closes https://github.com/vercel/next.js/issues/57923.
-
Lee Robinson authored
Closes https://github.com/vercel/next.js/issues/57816.
-
vercel-release-bot authored
-
Shu Ding authored
The allowlist should be origin domains that are allowed to send the requests, not the list of forwarded hosts (i.e. reverse proxies).
-
OJ Kwon authored
### What recent define_env refactoring removed usage of separate distDir from project config.
-
Tobias Koppers authored
* https://github.com/vercel/turbo/pull/6376 <!-- OJ Kwon - feat(turbopack): support url rewrite behavior options --> * https://github.com/vercel/turbo/pull/6386 <!-- OJ Kwon - feat(turbopack-ecmascript): support relative url asset ref --> * https://github.com/vercel/turbo/pull/6382 <!-- Tobias Koppers - refactor and fix CssEmbed for url() -->
-
OJ Kwon authored
### What I want to mimic webpack config's behavior (https://github.com/vercel/next.js/blob/9b4b0847ed4a1025e73bec16a9ee11766e632e14/packages/next/src/build/webpack-config.ts#L1381-L1385) to the pages/api in turbopack. PR attempt to create a new context corresponding to pages/api, and use it to create api chunks. Currently it just creates a new context, there is no new behavior's being introduced yet. I'm hoping to connect dots with https://github.com/vercel/turbo/pull/6376 later.
-
Sebastian Markbåge authored
React can emit a `Link:` header for preloads instead of `<link rel="preload">` in certain scenarios when that can be useful. This works by listening to the `onHeaders` event. In particular it's interesting for PPR because if you have something dynamic outside a Suspense boundary it generates an empty payload without any preloads in it. That's because when we do render the real shell we don't know what the document will look like. However, we can emit the `Link` header for CSS, images and font preloads that we've already discovered. In effect, even a dynamic page gets PPR benefits by early fetching resources. Custom headers is supported for static a ROUTE but not a PAGE. So I had to add similar wiring to forward headers when it's a page being rendered. It's important that this works every where, including dynamic routes, because otherwise we might miss out on preloads that we previously would've had.
-
Lee Robinson authored
https://nextjs.org/docs/pages/building-your-application/rendering/incremental-static-regeneration already correctly redirects.
-
vercel-release-bot authored
-
JJ Kasper authored
Ensures we don't await un-necessarily.
-
Lee Robinson authored
Small visual things and one busted link.
-
Wyatt Johnson authored
Co-authored-by:Zack Tanner <1939140+ztanner@users.noreply.github.com>
-
- 07 Nov, 2023 2 commits
-
-
Josh Story authored
Updates React from 08a39539f to 2983249dd. ### React upstream changes - https://github.com/facebook/react/pull/27641 - https://github.com/facebook/react/pull/27661 - https://github.com/facebook/react/pull/27640 - https://github.com/facebook/react/pull/27595 - https://github.com/facebook/react/pull/27600 - https://github.com/facebook/react/pull/27598 - https://github.com/facebook/react/pull/27590 - https://github.com/facebook/react/pull/27606 - https://github.com/facebook/react/pull/27608 - https://github.com/facebook/react/pull/27601 - https://github.com/facebook/react/pull/27616 - https://github.com/facebook/react/pull/27615 - https://github.com/facebook/react/pull/27614 - https://github.com/facebook/react/pull/27599 - https://github.com/facebook/react/pull/27597 - https://github.com/facebook/react/pull/27525 - https://github.com/facebook/react/pull/27571 Updates @types/react to 18.2.37 Updates @types/react-dom to 18.2.15
-
vercel-release-bot authored
-