fast-uri breaking changes
Every breaking API change we have recorded in fast-uri on npm: 4 breaking changes in 1 version. Below are its newest version, removals and renames first, each with its source.
Newest change October 19, 2026
On this page
3.1.9
- Behavior changed
Domain hosts with ambiguous delimiters or stripped control characters now raise an error instead of being silently rewritten. Callers must supply well-formed hosts. github.com - Behavior changed
Path-only suffix references whose first segment contains a colon are now escaped, so the output string differs from earlier versions. github.com - Behavior changed
Relative-reference normalization now preserves resolution semantics, so resolved output for some relative references may differ from earlier versions. github.com - Behavior changed
Schemes written with percent-encoding, such as ht%74ps:, are no longer decoded into a live scheme and are treated as malformed. Code that relied on that decoding must pass the plain scheme. github.com
Check your code
These are the changes. To see which of them reach your code, scan a public repository, or have your coding agent call check_code with your manifest or lockfile over MCP. The API reads every change in every version, not only the newest. On Team and up, a fix pull request opens for the changes that reach a connected repository. Nothing merges or deploys.
Put your code on continuous management.
Scan a public repository now, or give your agent one line.
See how out of date your code is.
Tell your agent what changed since it was trained.
claude mcp add --transport http since https://api.since.dev/mcp