ta
TanStack
GitHub
router
Workspace
GitHub
CI Pipeline Executions
Current execution
Failed
perf/default-search-parse-guard
Runs and Agents
Configuration
Self-Healing CI
Project Graph
Circular Dependencies
Enterprise
Resource Usage
Analysis
Conformance
Enterprise
Runs
Current run
Succeeded
Tasks
Resource Usage
Insights
Compare tasks
Analytics
Sign in
Toggle sidebar
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 run-many --target=build --exclude=examples/** --exclude=e2e/**
⌘K
Succeeded
nx run-many --target=build --exclude=examples/** --exclude=e2e/**
Click to copy
Linux
4 CPU cores
0773d0cf
7665
Get faster results
Learn how to enable distribution.
Atomizer enabled
43 groups of tasks optimized.