Run details

routerWorkspace

CI Pipeline Executions
- Current executionSucceeded
  schiller-manuel-link-one-key-set-layer
- Runs and Agents
- TimelineBeta
- Configuration
- Self-Healing CI
- Project Graph
- Circular DependenciesEnterprise
- Resource Usage
- Analysis
- ConformanceEnterprise
Runs

Insights

Compare tasks
Analytics

refactor(react-router): one key set and one assembly path for Link props The client and the server each kept their own copy of the 35 option names: the client as an object-rest destructure, the server as a Set. The two paths then assembled the result differently, with an eleven-spread external return and a fourteen-entry literal on the client and a fill-in-place sequence on the server. Both now share two helpers. `collectElementProps` copies every option the router does not consume, using one `ROUTER_OPTION_KEYS` set plus the two host rules (`Link` hosts never render `type`, an anchor has no `disabled`). `applyLinkState` finishes a router-controlled link: the selected state props, then the routing attributes and the merged class and style. It is the one place that defines precedence and absorbs `resolveStateProps`. The client adds its composed handlers between the two; the server adds nothing. External links return the collected props with `ref` and `href`. Element props therefore pass through as given instead of being stripped and re-added: external links forward them verbatim, falsy values included, and `useLinkProps` returns `children` for router-controlled links as it already did for external ones. Class and style are assigned only when the link or its state props provide one, so links without them carry no `undefined` keys and empty strings are still dropped. Measurements (macOS arm64, Node 24.8.0, local, against the previous commit): - react-router.minimal gzip 86019 -> 85984 (-35); -28 against the stack base, which this branch previously exceeded by 7. - Link client paired runner (3 repeats): shared-params CPU -13.8%, unique-params -11.4%, middleware -8.6%, encoding -13.2%, active -16.9%, all "faster". A 35-key object rest costs about 440 ns per call, the key set copy about 50 ns. - Link SSR paired runner (6 repeats): +0.4% to +1.5%, inside the runner's +/-4% noise floor measured head-against-head. SSR bundle 189850 -> 189523. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

nx run-many --target=build --exclude=examples/** --exclude=e2e/**

Succeeded

4 CPU cores

read access token used

c14ae46e8401

Get faster results

Learn how to enable distribution.

Atomizer enabled

43 groups of tasks optimized.

© 2026 - Nx Cloud

Terms of Service Privacy Policy Changelog Status Docs Contact Nx Cloud Pricing Company @NxDevTools

routerWorkspace