rsnext/test/e2e/app-dir/actions/next.config.js

/** @type {import('next').NextConfig} */
module.exports = {
  productionBrowserSourceMaps: true,
  logging: {
    fetches: {},
  },
}
Add experimental React related warning (#47986) For now, this isn't a strong requirement as normal `fetch` requests will still work with `react@next`. But in the future, form related props e.g. `action=` and `formAction=` requires the experimental build. Fixes NEXT-954. 2023-04-10 14:37:23 +02:00			`/** @type {import('next').NextConfig} */`
Add request callback in Flight client (#46650) Adding the `callServer` option to Flight client with a naive implementation. Fixes NEXT-393. ## Bug - [ ] Related issues linked using `fixes #number` - [x] Integration tests added - [ ] Errors have a helpful link attached, see [`contributing.md`](https://github.com/vercel/next.js/blob/canary/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` - [ ] [e2e](https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) tests added - [ ] Documentation added - [ ] Telemetry added. In case of a feature if it's used or not. - [ ] Errors have a helpful link attached, see [`contributing.md`](https://github.com/vercel/next.js/blob/canary/contributing.md) ## Documentation / Examples - [ ] Make sure the linting passes by running `pnpm build && pnpm lint` - [ ] The "examples guidelines" are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md) 2023-03-01 21:28:01 +01:00			`module.exports = {`
Add test case for client sourcemaps (#49308) This PR adds a test case to ensure that the server reference doesn't expose actual content of the original file in its sourcemap. Closes NEXT-1041. 2023-05-05 16:23:04 +02:00			`productionBrowserSourceMaps: true,`
Move logging option to stable (#56791) We introduced a data fetching logging before, and the control option was under experimental. After a bit experiments turns out users really loves it. We decide to move it to a stable option. ### Changes We're going to move the `logging` option outside of `experimental`, and scope the `fetches` related config under `logging.fetches`. ```js // next.config.js logging?: { fetches?: { fullUrl?: boolean } } ``` 2023-10-23 20:45:00 +02:00			`logging: {`
			`fetches: {},`
Add request callback in Flight client (#46650) Adding the `callServer` option to Flight client with a naive implementation. Fixes NEXT-393. ## Bug - [ ] Related issues linked using `fixes #number` - [x] Integration tests added - [ ] Errors have a helpful link attached, see [`contributing.md`](https://github.com/vercel/next.js/blob/canary/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` - [ ] [e2e](https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) tests added - [ ] Documentation added - [ ] Telemetry added. In case of a feature if it's used or not. - [ ] Errors have a helpful link attached, see [`contributing.md`](https://github.com/vercel/next.js/blob/canary/contributing.md) ## Documentation / Examples - [ ] Make sure the linting passes by running `pnpm build && pnpm lint` - [ ] The "examples guidelines" are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md) 2023-03-01 21:28:01 +01:00			`},`
			`}`