- 24 Feb, 2023 4 commits
-
-
JJ Kasper authored
-
JJ Kasper authored
-
JJ Kasper authored
Follow-up to https://github.com/vercel/next.js/pull/46317 this ensures same page case is handled as well. ## Bug - [x] 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)
-
JJ Kasper authored
This ensures we set `lastModified` when pulling from upstream cache instead of using `isStale` on the cache entry since once it's stored to the memory cache the `isStale` field would never be updated.
-
- 23 Feb, 2023 30 commits
-
-
Lee Robinson authored
Co-authored-by:
kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com> Co-authored-by:
Tim Neutkens <tim@timneutkens.nl> Co-authored-by:
Balázs Orbán <info@balazsorban.com>
-
Balázs Orbán authored
Until #45819 is landed, we should have the `compat` version (#45919), since the template has a `pages` folder. [Slack thread](https://vercel.slack.com/archives/C03KAR5DCKC/p1677183585403679) ## Bug - [ ] Related issues linked using `fixes #number` - [ ] 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)
-
JJ Kasper authored
Follow-up to https://github.com/vercel/next.js/pull/46283 this ensures we properly handle redirects with matchers at the base and we don't use the normalized redirects when generating the filter as the breaks with i18n. x-ref: [slack thread](https://vercel.slack.com/archives/C040J1CGLHH/p1677028542232619) ## Bug - [x] 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)
-
Jan Kaifer authored
fix #46260
-
JJ Kasper authored
-
JJ Kasper authored
-
JJ Kasper authored
-
Jimmy Lai authored
-
JJ Kasper authored
-
JJ Kasper authored
x-ref: [slack thread](https://vercel.slack.com/archives/C04DUD7EB1B/p1677165000745519) ## Bug - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Errors have a helpful link attached, see [`contributing.md`](https://github.com/vercel/next.js/blob/canary/contributing.md) --------- Co-authored-by:
Jimmy Lai <laijimmy0@gmail.com>
-
Hannes Bornö authored
Include the command to run the codemod in the warning. ## Bug - [ ] Related issues linked using `fixes #number` - [ ] 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) --------- Co-authored-by:
Steven <steven@ceriously.com>
-
Steven authored
- Fixes https://github.com/vercel/next.js/issues/46019 - Related to https://github.com/facebook/react/issues/25883 --------- Co-authored-by:
kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
-
Andy authored
I was notified that this link is broken. Not sure if I'm missing something, but the Markdown doesn't look right, changed it to be a normal link. ## Documentation / Examples - [x] Make sure the linting passes by running `pnpm build && pnpm lint` - [x] The "examples guidelines" are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md)
-
Shu Ding authored
Closes #44293. ## 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)
-
Nick Anisimov authored
## Bug - [x] Related issues linked using `fixes #number` - [ ] 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 - [x] 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) Fixes #46261
-
Tim Neutkens authored
-
Jiachi Liu 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: --> Closes NEXT-620 Test with app-playground locally on windows VM ## Bug - [x] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Errors have a helpful link attached, see [`contributing.md`](https://github.com/vercel/next.js/blob/canary/contributing.md) --------- Co-authored-by:
kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
-
Hannes Bornö authored
Add `built-in-next-font` to the codemods page. ## Documentation / Examples - [x] Make sure the linting passes by running `pnpm build && pnpm lint` - [x] The "examples guidelines" are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md) Co-authored-by:
Jimmy Lai <laijimmy0@gmail.com>
-
Tim Neutkens authored
-
Michael Webb authored
We replace neo4j-graphql-js with @neo4j/graphql and update Apollo server to version 4. This refactor also changes the code from Javascript to Typescript. ## Bug - [ ] Related issues linked using `fixes #number` - [ ] 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 - [x] Make sure the linting passes by running `pnpm build && pnpm lint` - [x] The "examples guidelines" are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md)
-
Tobias Koppers authored
# Features * https://github.com/vercel/turbo/pull/3923 # Bug Fixes * https://github.com/vercel/turbo/pull/3931 * https://github.com/vercel/turbo/pull/3933
-
JJ Kasper authored
Follow-up to https://github.com/vercel/next.js/pull/46287 this updates how we load the cache handler for the incremental cache so it's compatible with edge and also adds regression testing with a custom handler.
-
Tim Neutkens authored
-
JJ Kasper authored
x-ref: https://github.com/vercel/next.js/pull/46271 x-ref: https://github.com/vercel/next.js/pull/46081
-
JJ Kasper authored
This adds a new client router filter for app paths and redirects so that we correctly hard navigate when a transition for one of this paths is encountered. This fixes the longstanding issue where redirects weren't applied on the client so a redirect that matches a dynamic route as well would transition to the dynamic route on client transition but not on direct visit. Similarly this ensures we hard navigate to app paths from pages even if a page dynamic route matches the path. The specific filter leveraged here is a bloom filter as we can tolerate some false matches (currently targeting an error rate of `2%`) as they just trigger a hard navigation which should be acceptable and this also avoids needing to send an entire manifest with the related paths. We can leverage a manifest for the generated SSG paths as well in a follow-up to fix `fallback: false` routes not being navigated correctly on client-transition in some cases as well. The filter is initially behind an `experimental.clientRouterFilter` flag in `next.config.js` although this is auto-enabled when leveraging app directory to ensure proper transitions. fixes NEXT-609 closes: https://github.com/vercel/next.js/pull/46235 x-ref: [slack thread](https://vercel.slack.com/archives/C035J346QQL/p1677028663246719) x-ref: https://github.com/vercel/next.js/issues/41344 x-ref: https://github.com/vercel/next.js/issues/40062 x-ref: https://github.com/vercel/next.js/issues/37889 x-ref: https://github.com/vercel/next.js/discussions/26426 x-ref: https://github.com/vercel/next.js/issues/35837 ## Bug - [x] 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)
-
Chanhee Lee authored
Correct the spelling of the `OgTypFields` variable name to `OgTypeFields` in `resolve-opengraph.ts`.
-
Rich Haines 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: --> This PR updates the Edge Runtime docs on the next.js docs site with simplified tables for each API section ## Bug - [ ] Related issues linked using `fixes #number` - [ ] 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) --------- Co-authored-by:
JJ Kasper <jj@jjsweb.site>
-
Shu Ding authored
These loader rule changes should speed up compilation a bit as regexp matches should be way faster than function calls with loop and `includes` inside (`isResourceInPackages` is expensive), especially when the project is large. ## Bug - [ ] Related issues linked using `fixes #number` - [ ] 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)
-
Will Binns-Smith authored
Update Turbopack to turbopack-230222.3 ## Features * https://github.com/vercel/turbo/commit/01a004e3f6f30e793f037cc31f1ee5bff029181d ## Performance Improvements * https://github.com/vercel/turbo/commit/e575eb95a2b049657ec9ed22e88c8f8343068683 ## Misc * https://github.com/vercel/turbo/commit/a6f92743c3c3801a231464aba585a34dae71dfc9
-
Steven authored
This is a small refactor to image optimization tests. Previously, the `ctx` object was used for input options as well as next.config.js options but this PR separates the latter into `nextConfigImages`.
-
- 22 Feb, 2023 6 commits
-
-
Shu Ding authored
-
Jiachi Liu authored
Leverage edge build of react-server-dom-webpack on server and keep browser build of it for client build Closes NEXT-606 --------- Co-authored-by:kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
-
Shu Ding authored
Closes #45850. ## Bug - [ ] Related issues linked using `fixes #number` - [ ] 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) --------- Co-authored-by:
JJ Kasper <jj@jjsweb.site>
-
JJ Kasper authored
follow-up to https://github.com/vercel/next.js/pull/46081 gracefully handles no endpoint being available.
-
JJ Kasper authored
-
-