Skip to content

[pull] canary from vercel:canary - #1327

Merged
pull[bot] merged 4 commits into
code:canaryfrom
vercel:canary
Aug 22, 2026
Merged

[pull] canary from vercel:canary#1327
pull[bot] merged 4 commits into
code:canaryfrom
vercel:canary

Conversation

@pull

@pull pull Bot commented Aug 22, 2026

Copy link
Copy Markdown

See Commits and Changes for more details.


Created by pull[bot] (v2.0.0-alpha.4)

Can you help keep this open source service alive? 💖 Please sponsor : )

devjiwonchoi and others added 4 commits August 21, 2026 22:45
### Why?

Should come up with better solution that does not block PRs with git
conflict

x-ref:
https://vercel.slack.com/archives/C02CDC2ALJH/p1785263902728189?thread_ts=1785263687.502649&cid=C02CDC2ALJH

### How?

- Delete `errors.json`, the error-code SWC plugin, generated WASM, merge
driver, and validation/build tooling.
- Stop attaching error codes to server-rendering digests, redboxes, and
telemetry; native `Error.code` and `Error.name` remain available where
applicable.
- Remove the development-overlay error feedback UI, middleware, and
telemetry event that depended on stable codes.
- Update fixtures, snapshots, and guidance for code-free errors and
numeric-only digests.

<!-- NEXT_JS_LLM -->
…n a map (#97655)

This is a spiritual continuation of
#96114 . See
#94735 for motivation.

This codepath should already be pretty cheap, but in some cases (notably
inotify on Linux where updates aren't debounced as aggressively by the
OS) it could become somewhat hot and waste CPU while other
somewhat-CPU-heavy work is happening in other software (e.g. `pnpm`).

This removes two more sources of clones:
- If we only have a `&Path`, but it's already in the `paths` map, we can
use the raw entry API to avoid cloning it.
- `new_paths` can use `usize` indexes into the `FxIndexMap` instead of
storing another clone of the path. We could also encode this information
as flags on `path`, but the iteration over `new_paths` must happen as a
separate loop before the normal batch execution loop (near the bottom of
`DiskWatcher::watch_thread`), so I'd like to keep it as a separate data
structure to avoid having to filter out a bunch of unrelated keys
without the flag when finally processing the batch.
…(s) (#97710)

The `useSelectedLayoutSegment` and `useSelectedLayoutSegments` hooks
accept a
parameter named `parallelRouteKey` (singular), as declared in
`packages/next/src/client/components/navigation.ts`:

export function useSelectedLayoutSegment(parallelRouteKey: string =
'children')

The docs wrote it as `parallelRoutesKey` (plural) in three files, which
doesn't
match the generated `navigation.d.ts` type that editors surface via
IntelliSense:

- `use-selected-layout-segment.mdx` — parameter signature and
description
- `use-selected-layout-segments.mdx` — parameter signature and
description
- `parallel-routes.mdx` — "With useSelectedLayoutSegment(s)" section

Docs-only change; no behavior change.

---

Credit: This contribution was originally authored by @see-stack in
#97690 and is recreated here with signed commits.

Co-authored-by: Said Nasser <sdnssr001@gmail.com>
@pull pull Bot locked and limited conversation to collaborators Aug 22, 2026
@pull pull Bot added the ⤵️ pull label Aug 22, 2026
@pull
pull Bot merged commit 74a30b1 into code:canary Aug 22, 2026
16 of 19 checks passed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants