archive/rsnext

Author	SHA1	Message	Date
Tim Neutkens	f2ad08e2c8	Ensure tests suites have unique names (#56085 ) Currently these share the same name which makes it hard to track down which failed. I think this was accidental based on the previous `pnpm new-test` workflow. <!-- 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 # -->	2023-09-27 13:55:45 +02:00
JJ Kasper	199aa3c8f5	Add strict next head handling (#47938 ) This adds an `experimental.strictNextHead` flag to allow updating head tags tracking for pages to resolve the issue with runtime scripts being appended to the head element breaking the head tracking. Fixes: https://github.com/vercel/next.js/issues/11012 Fixes: https://github.com/vercel/next.js/issues/20682 x-ref: [slack thread](https://vercel.slack.com/archives/C051B8JAPQ9/p1680156608831939)	2023-04-05 08:29:36 +00:00
peter	3e5b0253e4	Fix document head with react 18 (#37443 ) Fix custom head on getInitialProps works with React 18 ## Bug - [ ] Related issues linked using `fixes #number` - [x] Integration tests added - [ ] Errors have helpful link attached, see `contributing.md` Co-authored-by: Jiachi Liu <4800338+huozhi@users.noreply.github.com>	2022-06-04 10:30:42 +00:00
Corbin Crutchley	fb23f7b642	chore: add test for in-fragment HEAD reflection (#35320 )	2022-05-22 23:35:53 -05:00
await-ovo	afbc511d3f	fix: place the charset meta tag at the top of the head (#36561 ) Fixes: #36432 ## Bug - [x] Related issues linked using `fixes #number` - [x] Integration tests added - [x] Errors have helpful link attached, see `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` - [ ] Integration tests added - [ ] Documentation added - [ ] Telemetry added. In case of a feature if it's used or not. - [ ] Errors have helpful link attached, see `contributing.md` ## Documentation / Examples - [x] Make sure the linting passes by running `yarn lint`	2022-05-22 17:28:54 +00:00
Tim Neutkens	62bb3482fe	Fix Fast Refresh for React 18 (#35718 ) - Updates the React 18 test suite to the latest React version. - Upgrade `react-refresh` module Fixes #35518 Fixes #35703 ## Bug - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Errors have helpful link attached, see `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` - [ ] Integration tests added - [ ] Documentation added - [ ] Telemetry added. In case of a feature if it's used or not. - [ ] Errors have helpful link attached, see `contributing.md` ## Documentation / Examples - [ ] Make sure the linting passes by running `yarn lint` Co-authored-by: Jiachi Liu <4800338+huozhi@users.noreply.github.com>	2022-03-30 12:16:17 +00:00
JJ Kasper	e8ca334d42	Fix non-concurrent function _document (#31628 ) This ensures functional `_document` is rendered correctly when not using concurrent mode. ## Bug - [x] Related issues linked using `fixes #number` - [x] Integration tests added - [ ] Errors have helpful link attached, see `contributing.md` Fixes: https://github.com/vercel/next.js/issues/31593 x-ref: https://github.com/vercel/next.js/pull/30156	2021-11-19 19:41:19 +00:00

7 commits