- 18 Aug, 2023 1 commit
-
-
vercel-release-bot authored
-
- 17 Aug, 2023 18 commits
-
-
vercel-release-bot authored
-
Zack Tanner authored
Follow up to https://github.com/vercel/next.js/pull/54081 -- this was restoring the router tree improperly causing an error on bfcache hits Had to override some default behaviors to prevent `forward` / `back` in playwright from hanging indefinitely since no load event is firing in these cases Fixes #54184 Closes NEXT-1528
-
Malte Ubl authored
`import { Listbox } from "@headlessui-float/react";` becomes `import { Listbox } from "@headlessui/react/dist/components/listbox/listbox";` -
Jiachi Liu authored
Fixes #52365 In #52275 that eslint config changed to a fixed canary version to leverage the improvement of `react-hooks` eslint plugin but breaks the installation when 3rd party packages having strict matching for certain version of eslint plugin. This PR allows both previous version and the canary version be present.
-
Jiachi Liu authored
Fixes #54174 We should only add default not-found boundary to loader tree components for root layout. It was accidently added for children routes before
-
Ben Brook authored
Closes #49774 (and my dupe https://github.com/vercel/next.js/issues/53141), where there's a type error when attempting to construct URLSearchParams from ReadonlyURLSearchParams, [as recommended in the Next docs here](https://nextjs.org/docs/app/api-reference/functions/use-search-params#updating-searchparams) and breaks `next build` on Node v18.16.0+, including on Vercel. This is blocked by TS publishing the new `dom` types (https://github.com/microsoft/TypeScript/issues/54466). The [URL Standard](https://url.spec.whatwg.org/#dom-urlsearchparams-size) added the size property to URLSearchParams (https://github.com/whatwg/url/pull/734) and this now has wide [browser support](https://developer.mozilla.org/en-US/docs/Web/API/URLSearchParams/size).
-
Justin Ridgewell authored
### What? Strip the relative path prefix (`_next/`) when generating the `PageLoaderAsset`. This is necessary because the page loader will internally use `__turbopack_load__`, which prepends the prefix back onto the path. ### Why? Without this, we'd try loading `_next/_next/path/to/file.js`, because we'd prepend the prefix onto a path that already contains it. ### How? When generating the page loader asset, we "proxy" the `OutputAsset` onto a path which has the prefix removed. ~~Depends on https://github.com/vercel/turbo/pull/5717~~ Closes WEB-1377
-
Justin Ridgewell authored
The current toolchain is very buggy. Closes WEB-1400
-
Steven authored
- Follow up to https://github.com/vercel/next.js/pull/54074
-
Shu Ding authored
These are not referenced anywhere in the codebase.
-
Jiachi Liu authored
For edge-runtime we always bundle, and all the mapping of internal ESM files are configured in webpack. Adding a new alias of "next/dist/build" so we don't have to manually check the mapping path for module proxy
-
vercel-release-bot authored
-
vercel-release-bot authored
-
Jiachi Liu authored
Reverts vercel/next.js#53578 This PR (#53578) will break client components test, revert it for now. Can repro by adding `"use client"` to `app/page.tsx` in `test/production/jest/server-only.test.ts` ``` FAIL app/page.test.jsx ● Test suite failed to run· Cannot find module 'private-next-rsc-mod-ref-proxy' from 'app/page.jsx'· Require stack: ``` -
vercel-release-bot authored
-
Jiwon Choi authored
- Added `has` to ResponseCookies in [edge-runtime/cookies#533](https://github.com/vercel/edge-runtime/pull/533) - Upgraded edge-runtime/cookies to 3.3.0 #54117 - Added a test case Fixes #54005 #54111
-
Will Binns-Smith authored
This: - Adds a simple, generic tracer in the client that can be subscribed to in order to report spans - Reports client spans through the HMR socket in the dev server - Receives these spans and includes them in `.next/trace` Closes WEB-1387
-
Max Leiter authored
### What? ~The `setTimeout(() => {}, 0)` was used in place of `setImmediate` due to lack of support in the Edge Runtime. This is no longer a problem.~ Not working like I expected. `ReadableStream.tee` should be widely supported as well as of [Node 16.5](https://developer.mozilla.org/en-US/docs/Web/API/ReadableStream/tee#browser_compatibility) ### Why? Use the platform! ### How? Use the built-in `ReadableStream.tee()`
-
- 16 Aug, 2023 18 commits
-
-
vercel-release-bot authored
-
Will Binns-Smith authored
Note: depends on next Turbopack publish https://github.com/vercel/turbo/pull/5487 exports a reusable `handle_issues` function for reporting issues and erroring when failing issues are encountered. This uses it for `next build` with a failing severity level of error.
-
Zack Tanner authored
Accidentally left this in after making some changes in: - https://github.com/vercel/next.js/pull/54081
-
Dima Voytenko authored
The internal IPC fetches are an internal framework detail and they shouldn't pollute the tracing in a non-verbose mode. Examples of internal fetch output: <img width="600" alt="image" src="https://github.com/vercel/next.js/assets/726049/64a25c02-bf39-4f54-8fe3-86018c7720dc"> <img width="1369" alt="image" src="https://github.com/vercel/next.js/assets/726049/f8f1d65c-5444-42c7-9e7d-6cdf9865eace">
-
Balázs Orbán authored
### What? When cloning a `Request` with `NextRequest` the second argument needs to take precedence over the `Headers` set on the original request. ### Why? Follow-up of #53157 I checked the `Request` spec https://fetch.spec.whatwg.org/#request-class and following the order of execution, `init.headers` should indeed override the headers if the first param was `Request`. I verified this in the browser too: ```js const req1 = new Request("http://n", {headers: {"x-header": "foo"}}) const req2 = new Request(req1, {headers: {"x-header-2": "bar"}}) Object.fromEntries(req2.headers) // {x-header-2: "bar"} ``` So we should match `NextRequest` with this behavior. ### How? Pass the `init` to `super` when cloning the request. Closes NEXT-1521 Fixes #54094
-
Will Binns-Smith authored
This adds an **opt-in** feature to send a subset of trace spans and metadata to a remote http server. The url must be provided as an option like so: `next dev --experimental-upload-trace=http://localhost:3000/traces` These traces are derived from the tracing data stored at `.next/trace`. The request payload looks like this: ```json { "metadata": { "commit": "69b0a3366734182f4efce6c0089c2592044d7124", "mode": "dev", "pkgName": "nextjs-project", "arch": "arm64", "cpus": 10, "platform": "darwin" }, "traces": [ [ { "traceId": "2f041a20b06027ab", "name": "hot-reloader", "id": 1, "timestamp": 28712742599, "duration": 21, "tags": { "version": "13.4.14-canary.1" }, "startTime": 1691707223226 }, { "traceId": "2f041a20b06027ab", "parentId": 1, "name": "webpack-invalidated-server", "id": 63, "timestamp": 28713776446, "duration": 244628, "tags": { "trigger": "manual" }, "startTime": 1691707224260 }, { "traceId": "2f041a20b06027ab", "parentId": 1, "name": "webpack-invalidated-server", "id": 111, "timestamp": 28714080210, "duration": 115267, "tags": { "trigger": "manual" }, "startTime": 1691707224563 }, { "traceId": "2f041a20b06027ab", "parentId": 1, "name": "webpack-invalidated-server", "id": 168, "timestamp": 28715243617, "duration": 69471, "tags": { "trigger": "[project]/pages/index.tsx" }, "startTime": 1691707225727 }, { "traceId": "2f041a20b06027ab", "parentId": 1, "name": "client-hmr-latency", "id": 222, "timestamp": 1691707225727000, "duration": 72000, "tags": { "clientId": 1691707224946 }, "startTime": 1691707225799 }, { "traceId": "2f041a20b06027ab", "parentId": 1, "name": "webpack-invalidated-server", "id": 223, "timestamp": 28716999898, "duration": 47425, "tags": { "trigger": "[project]/pages/index.tsx" }, "startTime": 1691707227483 } ] ] } ``` Currently only events of type `client-hmr-latency`, `hot-reloader`, `webpack-invalid-client`, `webpack-invalidated-server` are included, as well as all root spans. Traces are expected to include the ancestry of any given span through the `parentId` property.
-
Zack Tanner authored
When an mpa navigation takes place, we currently push the user to the new route and suspend the page indefinitely (x-ref: #49058). When navigating back, if the browser opts into using the [bfcache](https://web.dev/bfcache/), it will remain suspended and `pushRef.mpaNavigation` will be true. This means that anything that would cause the component to re-render will trigger the mpa navigation again (such as hovering over another `Link`, as reported in #53347) This PR checks to see if bfcache is being used by observing `PageTransitionEvent.persisted` and if so, resets the router state to clear out `pushRef`. Closes NEXT-1511 Fixes #53347
-
Steven authored
Since Next.js already requires [`node@16.8.0`](https://github.com/vercel/next.js/blob/88b8d15f41f894011cf33af0b1f4a3fb24aed46b/packages/next/package.json#L319) or newer, we can drop this workaround for squoosh/wasm on apple silicon. - x-ref: https://github.com/vercel/next.js/pull/27031
-
Jiachi Liu authored
Merge the rendering of `<LayoutRouter>` component into one place, with different props in different branches.
-
Will Binns-Smith authored
This ensures that corepack uses the correct package manager and version for the tmpdir install as it does for the rest of the repo. It reads the value from the root `package.json`. Closes WEB-1401
-
Steven authored
Since Next.js already requires [`node@16.8.0`](https://github.com/vercel/next.js/blob/88b8d15f41f894011cf33af0b1f4a3fb24aed46b/packages/next/package.json#L319) or newer, we can drop old techniques for removing a directory recursively and instead rely on the native [`fs.promises.rm()`](https://nodejs.org/api/fs.html#fspromisesrmpath-options) function (available since `node@14.14.0`). x-ref: https://github.com/vercel/next.js/pull/34210
-
Steven authored
This PR refactors some types to remove `as any`, but the runtime logic is the same.
-
Jiachi Liu authored
### What & Why Previously when rendering the root `/_not-found` in production, we'll always override the parallel routes component children with not-found component, this will break the navigation in build mode from root 404 `/_not-found` path. ### How The new solution is to change the root `/_not-found` rendering strategy. Previously the loader tree of `/_not-found` look like this ```js ['', { children: ['not-found', {}, {}] }, { layout: ..., 'not-found': ...} ] ``` it's not a pretty valid tree, which could lead to problems during rendering. New solution is to change the children to render a page, but the page content is `not-found.js` component. The new tree of root not-found will look like ```js ['', { children: ['__PAGE__', {}, { page: ... // same as root 'not-found' }] }, { layout: ..., 'not-found': ...} ] ``` This change could fix the navigation on the root not-found page. Fixes #52264 -
Kiko Beats authored
Hello, This PR upgrades `edge-runtime` and associated packages, mostly fixing issues.
-
Donny/강동윤 authored
### What? Update swc crates to https://github.com/swc-project/swc/commit/023042dfb9c941e95f2fc0e1cd9b245d0cc64aa5 ### Why? To apply https://github.com/swc-project/swc/pull/7813 ### How? Closes WEB-1396 Fixes #54054
-
Tim Neutkens authored
With the latest changes in stable Next.js setting HOSTNAME is not longer required for the image to function correctly
👍 Fixes #54093 -
Balázs Orbán authored
Follow-up of #54048. We changed the lock action from waiting 1 month to 2 weeks, but the wording was not reflecting it.
-
Damien Simonin Feugas authored
### 🧐 What's in there? This is another attempt to allow testing server-only code with Jest. ### 🧪 How to test? There's an integration tests which can be triggered with `pnpm testheadless server-only` Here is a more comprehensive setup: <details> <summary><code>app/lib/index.ts</code></summary> ```ts import 'server-only' export function add(num1: number, num2: number) { return num1 + num2 } ``` </details> <details> <summary><code>app/lib/index.test.ts</code></summary> ```ts import { add } from '.' it('adds two numbers', () => { expect(add(1, 3)).toEqual(4) }) ``` </details> <details> <summary><code>app/client-component.tsx</code></summary> ```ts 'use client' import { useState } from 'react' export default function ClientComponent() { const [text, setText] = useState('not clicked yet') return <button onClick={() => setText('clicked!')}>{text}</button> } ``` </details> <details> <summary><code>app/client-component.test.tsx</code></summary> ```ts import { fireEvent, render, screen } from '@testing-library/react' import ClientComponent from './client-component' it('can be clicked', async () => { render(<ClientComponent />) const button = screen.getByRole('button') expect(button).toHaveTextContent('not clicked yet') await fireEvent.click(button) expect(button).toHaveTextContent('clicked!') }) ``` </details> <details> <summary><code>app/server-component.tsx</code></summary> ```ts import { add } from '@/lib' export default function ServerComponent({ a, b }: { a: number; b: number }) { return ( <code role="comment"> {a} + {b} = {add(a, b)} </code> ) } ``` </details> <details> <summary><code>app/server-component.test.tsx</code></summary> ```ts import { render, screen } from '@testing-library/react' import ServerComponent from './server-component' it('renders', () => { render(<ServerComponent a={2} b={3} />) expect(screen.getByRole('comment')).toHaveTextContent('2 + 3 = 5') }) ``` </details> <details> <summary><code>app/page.tsx</code></summary> ```ts import Link from 'next/link' import ClientComponent from './client-component' import ServerComponent from './server-component' export default function Page() { return ( <> <h1>Hello World</h1> <Link href="/dave">Dave?</Link> <p> <ClientComponent /> </p> <p> <ServerComponent a={5} b={2} /> </p> </> ) } ``` </details> <details> <summary><code>app/page.test.tsx</code></summary> ```ts import { render, screen } from '@testing-library/react' import Page from './page' it('greets', () => { render(<Page />) expect(screen.getByRole('link')).toHaveTextContent('Dave?') expect(screen.getByRole('heading')).toHaveTextContent('Hello World') expect(screen.getByRole('button')).toHaveTextContent('not clicked yet') expect(screen.getByRole('comment')).toHaveTextContent('5 + 2 = 7') }) ``` </details> <details> <summary><code>app/[blog]/page.tsx</code></summary> ```ts import { Metadata } from 'next' import Link from 'next/link' type Props = { params: { blog: string } } export async function generateMetadata({ params: { blog: title }, }: Props): Promise<Metadata> { return { title, description: `A blog post about ${title}` } } export default function Page({ params }: Props) { return ( <> <div> <Link href="/">Back</Link> </div> <h1>All about {params.blog}</h1> </> ) } ``` </details> <details> <summary><code>app/[blog]/page.test.tsx</code></summary> ```ts import { render, screen } from '@testing-library/react' import Page from './page' it('has the appropriate title', () => { const title = 'Jane' render(<Page params={{ blog: title }} />) expect(screen.getByRole('heading')).toHaveTextContent(`All about ${title}`) expect(screen.getByRole('link')).toHaveTextContent('Back') }) ``` </details> <details> <summary><code>app/layout.tsx</code></summary> ```ts export default function RootLayout({ children }) { return ( <html lang="en"> <body>{children}</body> </html> ) } ``` </details> <details> <summary><code>jest.config.js</code></summary> ```ts const nextJest = require('next/jest') const createJestConfig = nextJest({ dir: './' }) module.exports = createJestConfig({ testEnvironment: 'jsdom', setupFilesAfterEnv: ['<rootDir>/test-setup.ts'], }) ``` </details> <details> <summary><code>package.json</code></summary> ```ts { "name": "rsc-test", "version": "0.0.0", "private": true, "scripts": { "test": "jest" }, "devDependencies": { "@testing-library/jest-dom": "latest" } } ``` </details> <details> <summary><code>test-setup.ts</code></summary> ```ts import '@testing-library/jest-dom' ``` </details> The app should run and all test should pass. ###❗ Notes to reviewers #### The problem: 1. next/jest configures jest with a transformer ([jest-transformer](https://github.com/vercel/next.js/blob/canary/packages/next/src/build/swc/jest-transformer.ts)) to compile react code with next -swc 2. the transformers configures next -swc for a given environment: Server or Client, based on jest global environment 3. Based on the environment, next -swc checks for invalid usage of `import('server-only')` `“use client”`, `export const metadata` or `export async function generateMetadata` 4. Because the global test environment is either jsdom or node, the same test suite can not include both client and server components #### Possible mitigations *A. Using jest projects* When configured with [multiple projects](https://jestjs.io/docs/next/configuration/#projects-arraystring--projectconfig), Jest can launch different runners with different environment. This would allow running server-only code in node and client-only code in jsdom. However, it requires user to completely change their jest configuration. It would also require a different setup when scaffolding new app-directory project with create-next. *B. Using doc blocks* Jest allows changing the environment per test file [with docBlock](https://jestjs.io/docs/configuration#testenvironment-string). However, by the time jest is invoking next -swc on a source file to transform it, this information is gone, and next -swc is still invoked with the (wrong) global environment. The PR #52393 provides a workaround for files with `import('server-only')`, but does not allow testing pages with metadata. *C. Always compile for node* Our jest-transformer could always configure next -swc for server: - pass Server-specific validations `import('server-only')` `export const metadata` or `export async function generateMetadata` - does not complain about `"use client"` This is what this PR is about! Fixes #47299 Co-authored-by:Jiachi Liu <4800338+huozhi@users.noreply.github.com>
-
- 15 Aug, 2023 3 commits
-
-
OJ Kwon authored
<!-- 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 - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating 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 # --> ### What? Leaving a small note to the build steps to avoid regressions like https://github.com/vercel/next.js/issues/54017 later. Closes WEB-1386 --------- Co-authored-by:
Steven <steven@ceriously.com>
-
stefanprobst authored
Currently, Next.js enforces that `forceConsistentCasingInFileNames: true` is added to a user's `tsconfig.json`. This PR removes that behavior for CNA templates, and when the typescript version is >= 5.0.0, because since ts 5.0 `forceConsistentCasingInFileNames` is `true` by default. See https://devblogs.microsoft.com/typescript/announcing-typescript-5-0/ related: https://github.com/vercel/next.js/issues/45617
-
OJ Kwon authored
### What? wasm-bindgen's serde deserialization is more strict to not automatically coerce non-optionable default values for the mdx configurations. Since these are required options anyway, consolidate to construct default options. Closes WEB-1384
-