Overview - Router

router

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Failed
7665
Environment issue→
b4a33036 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.
by Yagiz Nizipli