Package selection guidance compiled from public package information, community data, and project usage.
The uri package provides utilities for constructing, parsing, and manipulating URIs in Dart applications. It supports RFC 6570-compliant URI template parsing, enabling dynamic URL generation with variables. Designed for use across all major platforms, it integrates seamlessly into HTTP clients and web service integrations. The package is maintained by Google and offers a lightweight, reliable solution for handling complex URI operations in Flutter and Dart projects.
Use cases
Building dynamic API URLs
Parsing query parameters from URIs
Expanding URI templates with variables
Handling relative and absolute URIs
Integrating with HTTP clients
Validating URI structure
Key features
RFC 6570 URI template support
Robust parsing and construction
Cross-platform compatibility
Lightweight and efficient
Supports query string manipulation
Extensible for custom URI logic
Suitable for
API clients
Web service integrations
URL routing systems
Data fetching pipelines
Backend communication layers
Testing HTTP interactions
Considerations
Requires manual handling of encoding for special characters
Not intended for full URL validation beyond syntax
Limited to URI-level operations, not full HTTP requests
No built-in caching or retry mechanisms
Depends on correct usage of template syntax
May need pairing with http package for complete HTTP workflows
Original README
Original README snapshot from the linked source repository. Visit the repository for the latest content.
Utilities for working with URIs in Dart, mostly parsing and generating URIs.
UriPattern
UriPattern is an interface for classes that match and parse URIs, much like the Pattern is for Strings. It defines the methods bool matches(Uri uri) and UriMatch match(Uri uri).
UriMatch
UriMatch is the result of UriPattern.match(). It contains the parameters parsed out of a URI and the "rest" of the URI left over after parsing, which is useful for parsing a single URI with multiple relative URI patterns that form a hierarchy.
UriTemplate
UriTemplate is an implementation of RFC 6570 URI Templates. URI Templates are useful for generating URIs from data. UriTemplates are created from a template string, and then expanded with data to generate a URI:
URI templates are strings made up of fixed and variable parts. The variable parts are described with expressions, which are places within single curly-braces: { and }.
Expressions consist of an optional operator and a comma-separated list of variable specifications_. Variable specifications consist of a variable name and an optional modifier. The operator applies to the whole expression and controls how reserved characters are expanded, the prefix and separator, if any, applied to the expansion, and whether to expand the variable as a key/value pair. Modifiers apply to each variable in the expression and allow truncating the value, or "exploding" list and maps into multiple key/value pairs.
Examples
http://example.com/~{username}/
http://example.com/dictionary/{term:1}/{term}
http://example.com/search{?q,lang}
Operators
URI template expansions does more than simple variable replacement, it has facilities for generating paths, fragments, query strings and more. To control the expansion, expressions can use one of the supported operators:
Operator
Description
none
Simple string expansion
+
Reserved string expansion
#
Fragment expansion
.
Label expansion, dot-prefixed
/
Path segments, slash-prefixed
;
Path-style parameters, semicolon-prefixed
?
Form-style query, ampersand-separated
&
Form-style query continuation
Modifiers
Modifiers control
Modifier
Description
none
Default expansion
:n
Prefix: use only the first n characters of the value
*
"Explode" the lists and maps into key/value pairs
UriParser
UriParser parses URIs according to a UriTemplate, extracting parameters based on the variables defined in the template.
Since URI Templates are not designed to be parsable, only a restricted subset of templates can be used for parsing.
Parsable templates have the following restrictions over expandable templates:
URI components must come in order: scheme, host, path, query, fragment.
There can only be one of each component.
Path expressions can only contain one variable.
Multiple expressions must be separated by a literal.
Only the following operators are supported: none, +, #, ?, &
Default and + operators are not allowed in query or fragment components.
Queries can only use the ? or & operator.
The ? operator can only be used once.
Fragments can only use the # operator
UriBuilder
UriBuilder is mutable container of URI components for incrementally building Uris.