Tracing support, routes types generation and URL builder client

8.0.0-next.0 (2025-07-30)

Bug Fixes

• accidental removal of safeStringify (1dcbc57)
• decodeURI unicode values in the URL, including route params and query string (f0c045d), closes #105

Features

• add encoreUrl helper (257af47)
• add matchRoute and parseRoute helpers (0114df2)
• add routeInfo and middlewareInfo helpers (bb83bde)
• add serializeCookie helper (3952cfc)
• add type-safe heleprs for creating URLs from routes and patterns (d4558a5)
• create proper class for new URLBuilder and make brisk route and redirect APIs type-safe (623fd0c)
• do not render status page for non-HTML requests (f205126), closes #100
• export mime-types package via helpers (eb5d0af)
• first version of generating the URL builder client (7aa48d9)
• introduce a new type safe URLBuilder with the ability to generate types (6181a50)
• introduce config.createRequestId method and remove usage of cuid2 (4e19034)
• introduce tracing channels (44e272f)
• move tokens to route JSON output (f2cd82d)
• remove StoreRouteNode in favor of RouteJSON (c091c13)
• restructure code for client generation and create client build (7bdc4b6)
• speed up response serialization (36ef522)
• store references for all middlewares (ed3ef29)
• trace non-stream response serialization (4069c2d)

BREAKING CHANGES

• The request.parsedUrl property is no longer of type UrlWithStringQuery, since
  url.parse method in Node.js has been deprecated. Instead, we use a custom implementation to
  decode the URI and split the query string from it.

• Router.match method now accepts an additional 3rd argument. Which is a boolean flag to tell if
  it should attempt to decode unicode values in the route params.

• The exception handler will no longer consider status pages
  when an API request is sent with the Accept header not accept HTML response

Full Changelog: v7.6.1...v8.0.0-next.0