taTanStack
GitHubrouterWorkspace
GitHub
  • CI Pipeline Executions
    • Current executionFailed
      perf/default-search-parse-guard
    • Runs and Agents
    • Configuration
    • Self-Healing CI
    • Project Graph
    • Circular DependenciesEnterprise
    • Resource Usage
    • Analysis
    • ConformanceEnterprise
  • Runs
    • Current runFailed
    • Tasks
    • Resource Usage
Insights
  • Compare tasks
  • Analytics
    perf(router-core): guard default search parser against throws defaultParseSearch ran JSON.parse on every leftover string search value. For plain strings (the common case, e.g. ?q=hello&f=live) JSON.parse throws a SyntaxError that parseSearchWith catches to keep the raw string — and constructing/throwing that error is the dominant cost. Add a couldBeJson guard that decides from the first non-whitespace character whether a value could be valid JSON. It is a superset of JSON's value-start grammar, so any string JSON.parse would accept still gets parsed (identical results); we only skip the guaranteed-throwing parse of non-JSON strings. Search params are parsed on every SSR request and every client navigation. In-situ before/after on defaultParseSearch: ~3.1x faster on mixed X-like queries, ~1.7x on an all-plain-string query.
    nx affected --targets=test:eslint,test:unit,test:e2e,test:types,test:build,build --parallel=3
Failed
0773d0cf7665
99%

Completed tasks

796 of 798 completed.

<1%

Failed tasks

1 of 798 failed.

<1%

Not executed tasks

2 of 798 tasks were not executed.

<1%

Potential flaky tasks

1 of 798 tasks retried.

5%

Cache hits

40 of 798 tasks used cache.

89%

Distribution saved time

22m 33s instead of 3h 31m 18s.

© 2026 - Nx Cloud

Terms of ServicePrivacy PolicyChangelogStatusDocsContact Nx CloudPricingCompany@NxDevTools