- 02 May, 2023 2 commits
-
-
vercel-release-bot authored
-
lijianan authored
use includes replace indexOf
-
- 01 May, 2023 24 commits
-
-
OJ Kwon authored
### What? - closes WEB-800 This PR mimics fallback google font behavior for the turbopack from https://github.com/vercel/next.js/pull/47428, replaces fallback to capsize and adjust read logics.
-
OJ Kwon authored
### What? Trying to close WEB-718. Since next.config can pass `Record<String, any>` for the env value, explicitly interop it.
-
Shu Ding authored
This env should only affect the teardown & restart process, instead of the `useWorkers` option. This also solves the problem of running `next dev` on StackBlitz (which has the env var set: https://github.com/vercel/next.js/issues/48964#issuecomment-1528569879). Closes #48964.
-
Steven authored
fix NEXT-1003 Co-authored-by:Wyatt Johnson <633002+wyattjoh@users.noreply.github.com>
-
lijianan authored
### What? remove useless React.Fragment tag ### Why? <img /> is a single element, No need `<></>` as an outer wrapper ### How?
-
Jimmy Lai authored
-
Shu Ding authored
This PR renames `experimental.experimentalReact` as `experimental.serverActions` and makes it a hard compilation error if it's not set but detected server actions.
-
Ngô Đức Anh authored
### What? This PR fixes middleware's edge-chunks not being copied in copyTracedFiles. ### How? Merging its files' handling with other pages' ones. ### Note I also want to exclude `process.turbopack` from the unsupported APIs list by checking if `key === 'turbopack'` in `createProcessPolyfill` and `warnForUnsupportedProcessApi`, but I want to have some opinion on this first as I don't know if `process.turbopack` works with the Edge runtime.
-
Ngô Đức Anh authored
### What? This fixes `next-types-plugin` causing Typescript to complain about CommonJS files importing ESM ones when `"type": "module"` is set but `experimental.typedRoutes` is not enabled. ### How? Always create a `.next/types/package.json` with `"type": "module"` instead of only doing so when `experimental.typedRoutes` is enabled. Fixes #49004
-
Alberto Vilches authored
A link to a third-party package in the docs directs you to the wrong page.
-
Daniel authored
-
vercel-release-bot authored
-
Shu Ding authored
This PR adds `position: absolute` to the router announcer container so it won't affect the layout of siblings / parents. Closes #48087. Co-authored-by:kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
-
Shu Ding authored
This PR does three things: - Vendors the package `react-server-dom-webpack@experimental` as `react-server-dom-webpack-experimental` similar to React and React DOM - Upgrades all vendored React packages - Re-lands the `experimentalReact` flag to switch between `@next` and `@experimental` channels of React for app dir. Fix NEXT-926.
-
Shu Ding authored
Not sure when it was introduced (this was a warning before), but it's failing on `canary` right now: https://github.com/vercel/next.js/actions/runs/4851306015/jobs/8645117315
-
vercel-release-bot authored
-
Tobias Koppers authored
### What? fixes handling of GlobalError interop adds a test case for client component bug ### Why? app dir client component interop is broken ### Turbopack changes * https://github.com/vercel/turbo/pull/4597 <!-- Tobias Koppers - add rspack to our benchmark suite --> * https://github.com/vercel/turbo/pull/4761 <!-- Tobias Koppers - Do not use interop logic on proxy modules -->
-
Alex Kirszenberg authored
See https://github.com/vercel/turbo/pull/4598 ### Turbopack changes * https://github.com/vercel/turbo/pull/4754 <!-- Justin Ridgewell - Match TS's extends resolution algorithm --> * https://github.com/vercel/turbo/pull/4598 <!-- Alex Kirszenberg - More fluent GraphTraversal API --> --------- Co-authored-by:
Tobias Koppers <tobias.koppers@googlemail.com>
-
Donny/강동윤 authored
### What? Update swc_core and `@swc/core`. ### Why? https://github.com/vercel/turbo/issues/4747 seems like a critical issue. ### How? - Fix WEB-969 ### Turbopack changes * https://github.com/vercel/turbo/pull/4688 <!-- OJ Kwon - ci(workflow): add appdir underscore test to subset --> * https://github.com/vercel/turbo/pull/4751 <!-- Justin Ridgewell - Cleanup "started server on" message --> * https://github.com/vercel/turbo/pull/4756 <!-- Donny/강동윤 - chore: Update `swc_core` to `v0.75.41` --> --------- Co-authored-by:
kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com> Co-authored-by:
Tobias Koppers <tobias.koppers@googlemail.com>
-
vercel-release-bot authored
-
vercel-release-bot authored
-
Tim Neutkens authored
Fixes a small bug where `layout` directly under `app` wasn't considered. <!-- 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(s) that you're making: ## For Contributors ### Improving Documentation or adding/fixing Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
-
vercel-release-bot authored
-
vercel-release-bot authored
-
- 30 Apr, 2023 6 commits
-
-
Shu Ding authored
Closes #48807. The issue seems to be introduced with recent React Float change, which isn't a real problem but a behavior change. Resources are layered by the `precedence` key and the style insertion logic can be simplified as "insert the new stylesheet right after the existing stylesheet in the same layer". When multiple stylesheets are inserted in the same render pass, their new order will be flipped. This is a nice feature so we can always maintain the order of resources that might conflict.
-
vercel-release-bot authored
-
Shu Ding authored
Related change: #49003. This PR makes sure that these related IntelliSense features are updated: ### Invalid <img width="842" alt="CleanShot 2023-04-30 at 19 33 06@2x" src="https://user-images.githubusercontent.com/3676859/235367543-3c64ebb9-47fd-48d9-a846-60ec39bf0d3b.png"> ### Region (`string`) <img width="822" alt="CleanShot 2023-04-30 at 19 33 29@2x" src="https://user-images.githubusercontent.com/3676859/235367567-249041cb-9f2b-4693-815d-347ff200244f.png"> ### Regions (`string[]`) <img width="487" alt="CleanShot 2023-04-30 at 19 34 20@2x" src="https://user-images.githubusercontent.com/3676859/235367609-503294d1-ec9b-4d04-9aa7-4e76636eca60.png"> ### Docs <img width="679" alt="CleanShot 2023-04-30 at 19 34 41@2x" src="https://user-images.githubusercontent.com/3676859/235367630-74be18ed-ffc7-4b2d-ae3f-0ad6a187b166.png">
-
Tim Neutkens authored
These were added early on based on some assumptions around how the params would be passed. In the actual implementation it works differently so these are just dead code. <!-- 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(s) that you're making: ## For Contributors ### Improving Documentation or adding/fixing Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
-
vercel-release-bot authored
-
Tim Neutkens authored
Follow-up to #48959, adds the right types after the renames of properties. <!-- 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(s) that you're making: ## For Contributors ### Improving Documentation or adding/fixing Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
-
- 29 Apr, 2023 8 commits
-
-
Shu Ding authored
When we enable `webpackBuildWorker` this module level `const apiRouteWarnings = new LRUCache({ max: 250 })` will be created in 3 workers, so users will see 4 outputs (last one is static optimization): <img width="740" alt="CleanShot 2023-04-29 at 20 20 38@2x" src="https://user-images.githubusercontent.com/3676859/235318861-2ec12e30-70b2-4b56-8a2e-df08d130c349.png"> This PR fixes that and now there's only 1. -
vercel-release-bot authored
-
vercel-release-bot authored
-
Tim Neutkens authored
### What? Whenever you navigated and a page suspended through `loading` or an error happened caught by `error` in the first level of segments (e.g. `/dashboard` but not `/dashboard/settings`) scroll would not be applied. This happened because the focus and scroll handling component is rendered as part of `InnerLayoutRouter` and the Suspense / Error boundary was rendered **around** `InnerLayoutRouter`. This behavior is incorrect as we still want to immediately scroll to the place where the loading is rendered. This PR fixes the behavior by allowing the scroll to apply to loading / error too. ### How? Moved the scrolling component around the loading/error/innerlayout boundary and added tests.
-
Jiachi Liu authored
### What? * Update google fonts for `next/font` with `scripts/update-google-fonts.js.` * Add npm script `pnpm update-google-fonts` ### How? Run `pnpm update-google-fonts`
-
Donny/강동윤 authored
### What? Update resolve rule for `@swc/helpers` => `node_modules/@swc/helpers` to `@swc/helpers/_` => `node_modules/@swc/helpers/_` to select only `@swc/helpers@v0.5.0`. ### Why? Previous rule make webpack merge `@swc/helpers@v0.4.x` and `@swc/helpers@v0.5.x` ### How? Closes WEB-948 Fixes #48593
-
Tobias Koppers authored
### What? add a test case ### Why? Some packages expect the default export of a commonjs module to be the whole exports object when importing from ESM. turbo PR: https://github.com/vercel/turbo/pull/4738
-
lijianan authored
This handles the case when `Infinity` is passed to the Image `width` prop
-