NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
npm
A small and fast library for validating, parsing, and resolving URIs and IRIs
Latest stable
2.0.2
Last release today
14 Nov 2026
Ships unpredictably
gaps range from 2 weeks to 1.4 years
Rarely documented
notes for 3 of 20 stable releases
Nothing withdrawn
no release was ever pulled
4 years old
20 releases · first in 2023
Drag across the ruler to compare, or tap a release to open it.
Rewrote the readme, with an example, what the package offers, and a link to each page of the documentation at https://hyperjump.io/uri/ .
No code changes.
Full changelog: v2.0.1...v2.0.2
The readme and the package's homepage point to the documentation at https://hyperjump.io/uri/ .
No code changes.
homepage point to the documentation at https://hyperjump.io/uri/.Full changelog: v2.0.0...v2.0.1
Your coding agent can read these notes before it upgrades. Set up the MCP server →
A rewrite of @hyperjump/uri . The documentation is now at https://hyperjump.io/uri/ .
A rewrite of @hyperjump/uri. The documentation is now at https://hyperjump.io/uri/.
http, https, file, urn, tag, did, and data, as well as the generic syntax. Other schemes are checked with the generic syntax only. See Schemes.Iri and AbsoluteIri mark the strings that were checked. See Validate and parse.normalizeIri and normalizeUri apply the scheme's normalization too. See Normalize.assert functions and error classes. assertIri and the other assert functions throw an InvalidUriError or an InvalidIriError that says what's wrong and where.parseUrn, getScheme, hasScheme, getPath, getQuery, getFragment, and urlToIri, which makes a URL an IRI. See Convert URLs.is or assert function first.resolveIri, toAbsoluteIri, and toRelativeIri don't normalize their results.toRelativeIri takes the target first and the base second, and both have to be normalized.parseIri, resolveIri, toRelativeIri, and toAbsoluteIri.resolveIri doesn't take "" as a base.[v1.fe80::a+en1], are valid instead of throwing.See Migrate from v1 for each change and what to do about it.
This project publishes no release notes. Between v1.4.1 and v2.0.0 there were 70 commits, 69 of them substantive:
…and 49 more.
This project publishes no release notes. Between v1.4.0 and v1.4.1 there were 3 commits, 2 of them substantive:
This project publishes no release notes. Between v1.4.0 and v1.4.1 there were 3 commits, 2 of them substantive:
This project publishes no release notes. Between v1.3.9 and v1.4.0 there were 7 commits, 6 of them substantive:
This project publishes no release notes. Between v1.3.9 and v1.4.0 there were 7 commits, 6 of them substantive:
This project publishes no release notes. Between v1.3.8 and v1.3.9 there were 2 commits, 1 of them substantive:
This project publishes no release notes. Between v1.3.8 and v1.3.9 there were 2 commits, 1 of them substantive:
This project publishes no release notes. Between v1.3.7 and v1.3.8 there were 2 commits, 1 of them substantive:
This project publishes no release notes. Between v1.3.7 and v1.3.8 there were 2 commits, 1 of them substantive:
This project publishes no release notes. Between v1.3.6 and v1.3.7 there were 2 commits, 1 of them substantive:
This project publishes no release notes. Between v1.3.6 and v1.3.7 there were 2 commits, 1 of them substantive:
This project publishes no release notes. Between v1.3.5 and v1.3.6 there were 2 commits, 1 of them substantive:
This project publishes no release notes. Between v1.3.5 and v1.3.6 there were 2 commits, 1 of them substantive:
This project publishes no release notes. Between v1.3.4 and v1.3.5 there were 3 commits, 2 of them substantive:
This project publishes no release notes. Between v1.3.4 and v1.3.5 there were 3 commits, 2 of them substantive:
This project publishes no release notes. Between v1.3.3 and v1.3.4 there were 2 commits, 1 of them substantive:
This project publishes no release notes. Between v1.3.3 and v1.3.4 there were 2 commits, 1 of them substantive:
This project publishes no release notes. Between v1.3.2 and v1.3.3 there were 3 commits, 2 of them substantive:
This project publishes no release notes. Between v1.3.2 and v1.3.3 there were 3 commits, 2 of them substantive:
This project publishes no release notes. Between v1.3.1 and v1.3.2 there were 4 commits, 3 of them substantive:
This project publishes no release notes. Between v1.3.1 and v1.3.2 there were 4 commits, 3 of them substantive:
This project publishes no release notes. Between v1.3.0 and v1.3.1 there were 3 commits, 2 of them substantive:
This project publishes no release notes. Between v1.3.0 and v1.3.1 there were 3 commits, 2 of them substantive:
This project publishes no release notes. Between v1.2.2 and v1.3.0 there were 8 commits, 6 of them substantive:
This project publishes no release notes. Between v1.2.2 and v1.3.0 there were 8 commits, 6 of them substantive:
This project publishes no release notes. Between v1.2.1 and v1.2.2 there were 4 commits, 3 of them substantive:
This project publishes no release notes. Between v1.2.1 and v1.2.2 there were 4 commits, 3 of them substantive:
This project publishes no release notes. Between v1.2.0 and v1.2.1 there were 2 commits, 1 of them substantive:
This project publishes no release notes. Between v1.2.0 and v1.2.1 there were 2 commits, 1 of them substantive:
This project publishes no release notes. Between v1.1.0 and v1.2.0 there were 3 commits, 2 of them substantive:
This project publishes no release notes. Between v1.1.0 and v1.2.0 there were 3 commits, 2 of them substantive:
Nothing published for this version
Nothing published for this version
One column per quarter.