- 22 Jul, 2025 2 commits
-
-
nextjs-bot authored
-
Niklas Mischkulnig authored
-
- 18 Jul, 2025 1 commit
-
-
nextjs-bot authored
-
- 17 Jul, 2025 2 commits
-
-
Zack Tanner authored
When we updated `experimental.strictNextHead` to be true in #65418, we did not update all spots that would default to true in the case where the value was omitted entirely. This led to the default value not being correctly applied in pages router, which resulted in duplicate metadata w/ React 19. Since we made the flag the default, we can also probably clean up this flag all together, but that can be done separately. Fixes #81655 Fixes #81689
-
Jiachi Liu authored
-
- 15 Jul, 2025 2 commits
-
-
JJ Kasper authored
This ensures if using NextServer or a custom-server directly we honor the custom config passed in correctly. Backports to next-15-4 branch
-
nextjs-bot authored
-
- 14 Jul, 2025 19 commits
-
-
nextjs-bot authored
-
nextjs-bot authored
-
nextjs-bot authored
-
Luke Sandberg authored
[turbopack] Rename `traverse_edges_from_entries_topological` to `traverse_edges_from_entries_dfs` (#81481) ## Rename `traverse_edges_from_entries_topological` to `traverse_edges_from_entries_dfs` This PR renames the `traverse_edges_from_entries_topological` method to `traverse_edges_from_entries_dfs` to better reflect its actual behavior. The method performs a depth-first search traversal rather than a topological sort. The PR also: - Updates the method documentation to clarify that it performs a DFS traversal - Makes `ClientReferenceMapType` derive `Copy` for better ergonomics - Removes unnecessary `ResolvedVc::upcast` call in client references mapping - Renames some variables for clarity (`actions` → `client_references`) - Removes unused `module_graph_for_entries` function - Adds some tests for the traversal routine. Not very interesting for this traversal but should make it easier to test future traversals. These changes improve code clarity and correctness by ensuring the method name accurately describes its behavior.
-
Benjamin Woodruff authored
It should be equivalent, but it's clearer that the LHS is always visited
-
Steven authored
This fixes a handful of issues including: - https://github.com/lovell/sharp/issues/4393 - https://github.com/lovell/sharp/issues/4382 - https://github.com/lovell/sharp/issues/4398 - https://github.com/lovell/sharp/issues/4374 - https://github.com/lovell/sharp/issues/4417 See full list of changes https://github.com/lovell/sharp/compare/v0.34.1...v0.34.3
-
Benjamin Woodruff authored
Previously this was only parsing the first line of input ``` cargo run -p swc-ast-explorer <turbopack/crates/turbopack-tests/tests/snapshot/comptime/assignment/input/index.js | less ```
-
Jiachi Liu authored
-
Jiachi Liu authored
-
Joseph authored
Closes: [DOC-4741](https://linear.app/vercel/issue/DOC-4741/document-oninvalidate-for-userouter-hook)
-
Jude Gao authored
This PR fixed two typos that affected isHeadPartial logic.
-
Delba de Oliveira authored
Updates the docs to include the new options in 15.4. - `prefetch="auto"` option: https://github.com/vercel/next.js/pull/78689 - `next build` new `--debug-prerender option`: https://github.com/vercel/next.js/pull/80667 --------- Co-authored-by:
graphite-app[bot] <96075541+graphite-app[bot]@users.noreply.github.com>
-
Sebastian "Sebbie" Silbermann authored
-
Jiachi Liu authored
Format line format: `<segment> [<files,>]` This will help visualize the rendered segment explorer panel easier by checking the snapshot. e.g. ``` app/ [layout.tsx] parallel-routes/ [layout.tsx, page.tsx] @bar/ [layout.tsx, page.tsx] @foo/ [layout.tsx, page.tsx] ```
-
Tobias Koppers authored
### What? Fix a hanging compilation in a specific case when reexports modules in a cycle. Fix reported issues for tree shaken modules
-
Sebastian "Sebbie" Silbermann authored
-
Sebastian "Sebbie" Silbermann authored
-
Sebastian "Sebbie" Silbermann authored
-
Joseph authored
Partially Closes: https://linear.app/vercel/issue/DOC-4854/server-actions-v14-and-v13-links
-
- 13 Jul, 2025 2 commits
-
-
nextjs-bot authored
-
Hendrik Liebau authored
Something may have changed in infra that causes a fallback shell revalidation instead of the expected route shell revalidation. Until this is resolved we disable the deploy test to unblock.
-
- 12 Jul, 2025 4 commits
-
-
nextjs-bot authored
-
Rob Pruzan authored
-
Zack Tanner authored
**What:** `layout-router` currently forces style recalculation on every navigation by manipulating the `scroll-behavior` CSS property on the `<html>` element. This would impact most navigations, even though most don't use smooth scrolling **Why:** To prevent smooth scrolling during router navigation (which can feel janky), Next.js temporarily resets `scroll-behavior` to `auto`, then restores the original value (#40642). While this solves the UX issue, it causes performance overhead for the vast majority of users who don't have smooth scrolling configured. **How:** This PR introduces an optimization that checks for a `data-scroll-behavior="smooth"` attribute before manipulating styles. Only users who explicitly opt into smooth scrolling will experience the style recalculation. - The existing behavior is preserved by default - Opt-in to the new behavior by setting `experimental.optimizeRouterScrolling: true` in Next.js config - When smooth-scroll is detected on the document, a development warning is logged to notify that the default behavior will be changing in an upcoming major.
-
Zack Tanner authored
This function has a confusing name because it doesn't do any sort of smooth scroll handling or behavior, it just resets smooth scroll handling on the document before performing a router transition. This attempts to rename the function to be more accurate to what it's doing.
-
- 11 Jul, 2025 8 commits
-
-
nextjs-bot authored
-
Rob Pruzan authored
Previously we mounted event handlers on the the menu's [`ownerDocument`](https://developer.mozilla.org/en-US/docs/Web/API/Node/ownerDocument) to listen for clicks outside the menu. This causes a bug where the ref the useEffect captures is not set yet, and when it is set the effect does not try to run again. The fix is to derive active state from the true state tracking if the menu is mounted, not if the menu __will be open__ ### Before https://github.com/user-attachments/assets/d88f9b46-2203-45f3-a184-46db39584679 ### After https://github.com/user-attachments/assets/57a0f68f-8d46-41ea-b761-222c82e4b6bc
-
nextjs-bot authored
-
Sebastian "Sebbie" Silbermann authored
-
Nazar authored
docs: update Page example to use Promise-based params in 05-server-and-client-components.mdx (#81557) What? This PR updates the Page component example in 05-server-and-client-components.mdx to use Promise-based params as recommended in the Next.js 15 documentation. Why? Next.js 15 introduced support for async props, allowing the params prop to be a Promise in Server Components. Updating the documentation ensures that users follow the latest recommended practices and avoid confusion when working with dynamic routes in Next.js 15. How? - Changed the Page component example to accept params as a Promise and use await params to destructure the id. - Updated the type annotation accordingly.
-
Hendrik Liebau authored
This will allow us (again) to selectively use type-checked rules internally, as stipulated in #67689. In a follow-up, we'll likely add https://typescript-eslint.io/rules/switch-exhaustiveness-check/ as a first type-checked rule.
-
JJ Kasper authored
Adds a 60s timeout for fetching the cache to avoid this blocking continuing x-ref: https://github.com/ijjk/rust-cache/commit/a34594c450817c9860143c79797a8770c4e587f5
-
Niklas Mischkulnig authored
They are only ever used in dev. Closes PACK-4767
-