- 19 Sep, 2023 12 commits
-
-
vercel-release-bot authored
-
vercel-release-bot authored
-
Tobias Koppers authored
### What? makes sure that styled-jsx is always bundled as it contains `react` and it being external would break the react vendoring
-
Tobias Koppers authored
### What? Makes sure that errors that have no user code in stack trace still show an stack trace Closes WEB-1605
-
Jiachi Liu authored
`isAppLayer` condition was missing `app-metadata-route` layer, made it as a util now like other webpack layer utils, add metadata route layer to the group. Then `React.cache` can be available there. Also update regex to be compatible across platform Fixes #55561 Closes NEXT-1635
-
Maia Teegarden authored
Closes WEB-1600 Co-authored-by:JJ Kasper <jj@jjsweb.site>
-
Shu Ding authored
This addresses the case mentioned in https://github.com/vercel/next.js/pull/54925#pullrequestreview-1616315332. We can't optimize the case where we can't statically determine the type of the `useState` argument as it can be a function: `useState(() => ...)`.
-
Shu Ding authored
Follow-up for #55310.
-
Balázs Orbán authored
### What? Moving maintenance to a separate repository. ### Why? I want to make these actions reusable in other projects as they seem to work well in the Next.js repository. ### How? The code is moved to https://github.com/balazsorban44/nissuer I tested it on my fork, and all the following functionality is preserved: https://github.com/balazsorban44/next.js/issues/56 - [x] Close/lock/comment without a valid reproduction link - [x] Minimize "+1" - [x] Add labels based on user selection - [x] Add comment based on the maintainer's label (eg.: "please add a complete reproduction")
-
Zack Tanner authored
This consolidates how we're evaluating when to opt into `react@experimental` since it's sprinkled in a lot of spots. Also adds a new flag to opt into the experimental channel Closes NEXT-1632
-
Shu Ding authored
Feedback from https://github.com/vercel/next.js/issues/48748#issuecomment-1714292279. As per my testing, an App Router route of ```tsx 'use client' import { Button } from 'mui-core' export default function Page() { return <Button>Hi</Button> } ``` was improved from `2.4s (1221 modules)` to `1458ms (649 modules)` for the local dev.
-
romeobravo authored
### What? Fix heading hierarchy in revalidateTag documentation (https://nextjs.org/docs/app/api-reference/functions/revalidateTag) ### Why? Makes it consistent with https://nextjs.org/docs/app/api-reference/functions/revalidatePath
-
- 18 Sep, 2023 28 commits
-
-
vercel-release-bot authored
-
JJ Kasper authored
Seems we occasionally have unhandledRejections with `ensurePage` due to the our memoize handling not attaching `.catch` quick enough. This updates to ensure `.catch()` is always present for that promise and re-throwing separately. Also, ensures the necessary `module.compiled` files for `route-modules` are included in our build traces. x-ref: [slack thread](https://vercel.slack.com/archives/C04KC8A53T7/p1695072157528389?thread_ts=1695060035.024789&cid=C04KC8A53T7)
-
Matt Hooper authored
-
Alejandro Roigé authored
changed` failed `for `payment_failed` on line 45 ### What? Error in line 45 on type of payment_intent ### Why? Example provided does not work ### How? Added 'payment_'
-
vercel-release-bot authored
-
Jiachi Liu authored
We need to disable the default treat `middleware` and `pages/api` as server-only, unless users explictly import "server-only" to poison it. This will avoid the case that when a library is mixing "client-only" API and shared components API in one bundle, and the shared API is used in middleware or `pages/api` that might cause error. See the test case added. Follow up for #55394
-
Steven authored
- Follow up to https://github.com/vercel/next.js/pull/55544 - Same pattern from https://github.com/vercel/next.js/pull/49529
-
JJ Kasper authored
Adds explicit examples for route groups as those may not be obvious from existing examples. x-ref: https://github.com/vercel/next.js/issues/49387#issuecomment-1722575969
-
JJ Kasper authored
This ensures we properly set/restore the status code with ISR paths in app router so that when we set the 404 status code with `notFound` it is persisted properly. Fixes: https://github.com/vercel/next.js/issues/43831 Closes: https://github.com/vercel/next.js/issues/48342 x-ref: https://github.com/vercel/next.js/issues/49387#issuecomment-1722575969
-
Tobias Koppers authored
### What allow to build next.js on windows Closes WEB-1597 --------- Co-authored-by:JJ Kasper <jj@jjsweb.site>
-
vercel-release-bot authored
-
Leah authored
Closes WEB-1598
-
YOSHIKI authored
## For Contributors ### Improving Documentation - [x] Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - [x] Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### What? add bun run dev command to template readme for create-next-app
-
OJ Kwon authored
### What? Minor PR updates additional tests. Closes WEB-1572
-
Jimmy Lai authored
Some people are using `ReactDOM/server` in some contexts like App Routes and Server Actions. The changes in #55362 made it so that there were no more aliases if they wanted to use it so it would fallback to their versions of React, which might not include the APIs you would expect from canary. Also reverting the decision to proxy `ReactDOM/server` to `ReactDOM/server.edge` in the SSR layer as the APIs are not the same.
-
JJ Kasper authored
x-ref: [slack thread](https://vercel.slack.com/archives/C04DUD7EB1B/p1695039655548129)
-
OJ Kwon authored
### What? Update few test fixture setup doesn't invoke --turbo based on the conditions. Closes WEB-1543
-
OJ Kwon authored
### What? Enables the image extensions supported by turbopack. Also fixes test fixture to assert error overlay header. Closes WEB-1587
-
Balázs Orbán authored
### What? Removes Replay.io as a valid reproduction link from our bug template. ### Why? Based on issues https://github.com/vercel/next.js/issues/55181 and https://github.com/vercel/next.js/issues/55278 it looks like people are struggling to report the correct thing. Also, without source maps, replays are still harder to use for debugging than an actual code base Ref: [Slack thread](https://vercel.slack.com/archives/C04DUD7EB1B/p1694608481515339?thread_ts=1694428848.689079&cid=C04DUD7EB1B)
-
vercel-release-bot authored
-
Kevin authored
I added the application/json header to the API lib of the Prepr example. Because without it when statically generating an error is produced by GraphQL. Co-authored-by:kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
-
Jiachi Liu authored
### `useSearchParams` server router's query includes both search params and path params, this PR eliminate the path params from `useSearchParams` to make it aligned between app router and pages router ### `useParams` For pages, we extract the params keys with `getRouteRegex`, and pick them out from `router.query` Fixes #54242 Closes NEXT-1536
-
Jiachi Liu authored
Allow server-only in server targets and client-only in client components targets to be available (#55394) Users want to use `server-only` to restrict the middleware / app routes / pages api, but now it's failing as we're treating them as different webpack layers, but validating the `server-only` only with server components layers. Here we modify the rules a bit to let everyone can use "server-only" for the bundles that targeting server-side. For next-swc transformer, we introduce the new option `bundleType` which only has `"server" | "client" | "default"` 3 values: * - `server` for server-side targets, like server components, app routes, pages api, middleware * - `client` for client components targets such as client components app pages, or page routes under pages directory. * - `default` for environment like jest, we don't validate module graph with swc, replaced the `disable_checks` introduced [#54891](https://github.com/vercel/next.js/pull/54891). Refactor a bit webpack-config to adapt to the new rules, after that `server-only` will be able to used in the server-side targets conventions like middleware and `pages/api` Fixes #43700 Fixes #54549 Fixes #52833 Closes NEXT-1616 Closes NEXT-1607 Closes NEXT-1385
-
vercel-release-bot authored
-
Tim Neutkens authored
Found that the require hook has some overhead because of reading process.env. This removes the condition after Jimmy reviewed in #55494 as it seems to be no longer needed. Seems to improve RPS by about ~100.
-
Tobias Koppers authored
And sync deps so they don't conflict * https://github.com/vercel/turbo/pull/5959 <!-- Tobias Koppers - reduce number of task in async_module --> * https://github.com/vercel/turbo/pull/5960 <!-- Tobias Koppers - reduce unneccessary fs tasks --> * https://github.com/vercel/turbo/pull/5955 <!-- Tobias Koppers - bumping minor or major should reset patch/minor --> Closes WEB-1592 --------- Co-authored-by:
kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
-
vercel-release-bot authored
-
JJ Kasper authored
Now that we are bundling the react runtime for app router we can remove the esm loader as that was the reason it was added when bringing the server back into a single process. x-ref: https://github.com/vercel/next.js/pull/55362 --------- Co-authored-by:
kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
-