- 02 Nov, 2023 3 commits
-
-
vercel-release-bot authored
-
Zack Tanner authored
This removes our current convention of throwing promises in reducers in favor of returning promises that can be consumed by `use` instead. This will help unblock some future improvements (batching, PPR) Reducers that would typically throw a promise now return their promise. This gets maintained by a mutable queue (initialized in hydrate) to ensure actions are processed in-order. The queue is also responsible for mutating state and passing it as an input to subsequent actions. This PR does not modify reducer behavior to keep changes minimal, but there's more cleanup that we can do in a follow-up PR to remove things that previously assumed reducers would be replayed. (I recommend reviewing with whitespace turned off) --------- Co-authored-by:Tim Neutkens <tim@timneutkens.nl>
-
Steven authored
Since we separated unit tests into its own job in PR https://github.com/vercel/next.js/pull/55621, we can now run unit tests against Node.js 18 and Node.js 20 (maintenance and lts) using a matrix.
-
- 01 Nov, 2023 22 commits
-
-
vercel-release-bot authored
-
Wyatt Johnson authored
This passes down the route kind information to the incrememntal cache so it no longer needs to test some files existing in order to validate if the file exists or not for a route.
-
Zack Tanner authored
When postpone is caught by user code, this will cause PPR not to properly prerender the static parts and thus we need to fail the build. This also adds some messaging about how to fix the error. Prior to this change, catching code that would normally trigger `postpone ` would silently fail, but the build outputs would be incorrect as there's no postpone data available. Relands #57477 with additional tests & fixes
-
Balázs Orbán authored
### What? Drop redundant Jest config ### Why? This slipped in by accident. It's already the default value. See https://jestjs.io/docs/configuration#snapshotformat-object
-
OJ Kwon authored
### What Probably not a big deal since we run this against cjs / esm both, but looks like it's a minor typo. Closes WEB-1894
-
Jiachi Liu authored
This part was removed before but added in back during the merging of turbopack and legacy `next-swc` changes. Remove them again
-
Jiachi Liu authored
Social metadata will be display properly if there's `title` and `description` configured. If you have `title` and `description` configured in metadata, some people's intuition will be "yes I had them, they should be the same if I have `openGraph` or `twitter`". This PR improves the configuration that you don't have to configure them as duplicate both in top `metadata` export and `metadata.openGraph` or `metadata.twitter`. But we don't always assign them if you don't configure social cards (open graph or twitter), this way users should be able to omit social cards if possible. x-ref: [feedback from slack](https://vercel.slack.com/archives/C03KAR5DCKC/p1698548491415089?thread_ts=1698512393.500649&cid=C03KAR5DCKC)
-
Jiachi Liu authored
Reduce the confusiong of the the logging of pages, make it easier to understand * Removing the trailing `/page`, `/route` suffix * Removing the internal segment like `[[...__metadata__]]` #### After ``` ○ Compiling / ... ○ Compiling /dynamic/[slug]/icon ... ``` #### Before ``` ○ Compiling /page ... ○ Compiling /(group)/dynamic/[slug]/icon-ahg52g/[[...__metadata_id__]]/route ... ``` Closes NEXT-1701
-
Jon Meyers authored
### What? [1] Use Server Actions for auth [2] Use Geist font [3] Address warning about `metadataBase` in console ### Why? [1] The co-location of Login page and authentication logic is simpler for beginners [2] Looks nice [3] Avoid confusing people with the starter template printing warnings ### How? [1] Refactor Route Handlers to Server Actions [2] Install font and set to `html` [3] Explicitly declare the default value for `metadataBaseUrl`
-
Lee Robinson authored
-
Gal Schlezinger authored
make sure `next.config.mjs` uses `export` instead of `module.exports`
-
Balázs Orbán authored
### What? Minor change to use the word `content` instead of `HTML` in the build output tree-view legend. ### Why? The `○` symbol is also used for statically pre-rendered Route Handlers, which might not return HTML, so just clarifying the wording. [Slack thread](https://vercel.slack.com/archives/C03KAR5DCKC/p1698844583794019)
-
vercel-release-bot authored
-
vercel-release-bot authored
-
Shu Ding authored
This new option specifies a list of host names that are considered safe, to accept as Server Action requests if they're different from the initial request origin. It can be very helpful when the hosted app has many layers of reverse proxies ahead. Closes #57397.
-
Balázs Orbán authored
### What? Follow-up of #56797 While working on this, I noticed that some logic around stripping internal headers was duplicated, so I did some cleanup too. ### Why? In #56797 we set these headers, but it only affected Route Handlers, Middleware is still missing them, which is a regression introduced in #52492 (Related: https://github.com/vercel/next-learn/issues/252) ### How? Move to set these headers up to `base-server.ts` so they are present in Middleware too. > Note: All headers are set with `??=` to respect the original value if set (with other words, only add these headers if they aren't set yet) Closes NEXT- Fixes #52266
-
JJ Kasper authored
This reverts commit 907f3797. x-ref: https://github.com/vercel/next.js/pull/57346
-
vercel-release-bot authored
-
Zack Tanner authored
Updates React from 0c6348758 to 08a39539f. ### React upstream changes - https://github.com/facebook/react/pull/27634 - https://github.com/facebook/react/pull/27632
-
JJ Kasper authored
We noticed that our internal soft tags were unexpectedly including the query string for SSR routes which causes the URL soft tag to not match correctly so this ensures we properly normalize the value to just the pathname and not include the query.
-
Giovanni Fumagalli authored
I think that sometimes when a revalidation happens from a request with caching headers this causing the 304 status to be cached. This PR ensures the 304 from an initial response doesn't affect a background revalidation. Fixes: https://github.com/vercel/next.js/issues/56580 --------- Co-authored-by:
JJ Kasper <jj@jjsweb.site>
-
Lee Robinson authored
Remove examples that were linking to just READMEs, or outdated / discontinued ones.
-
- 31 Oct, 2023 15 commits
-
-
Jon Meyers authored
### What? [1] Simplify example [2] Refactor `delete` method to use `cookies.set` ### Why? [1] Make it easier to follow [2] Fix build errors ### How? [1] Adding comments and abstracting code into helper functions [2] Setting cookie to empty value when removed --------- Co-authored-by:Lee Robinson <me@leerob.io>
-
vercel-release-bot authored
-
Shu Ding authored
You can read the removed comments to get some context here. Based on the community feedback, we're removing this compile-time error and instead, it will be a runtime error only when it gets accessed by React and found it missing in the manifest. In the future, we'll need: - Converting the client references created this way to be specific errors. So they'll only throw in that certain case. - Or have a prepass compilation to collect all the references globally. This way we can support any kind of layer change. Related: https://twitter.com/trashh_dev/status/1719016700191150550.
-
Steven authored
-
SADIK KUZU 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 # --> Co-authored-by:
JJ Kasper <jj@jjsweb.site>
-
Jiachi Liu authored
Remove the unnecessary condition as we always use `route.page` for `reportTrigger`
-
Jiachi Liu authored
This reverts commit bd2e8732.
-
Jiachi Liu authored
-
vinay authored
Update `Explore the Next.js 13 playground.` --> `Explore starter templates for Next.js`
-
Jimmy Lai authored
bumping the vendored otel package
-
Zack Tanner authored
Currently we publish a release in GitHub before it's actually fully published to npm. This moves the undraft step until after the publish is finished
-
Zack Tanner authored
Removes some usernames that our PR labeler webhook shouldn't apply to
-
Tim Neutkens authored
Makes it easier to convert to TypeScript later when it has a consistent return type. <!-- 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 # -->
-
mknichel authored
This PR adds a tag to the `next-build` span to identify whether the build is using the webpack build workers and/or has a custom webpack config which can be used during debugging traces. 
-
Maia Teegarden authored
@vercel/web-tooling -> @vercel/turbopack
-