NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
pub.dev
pub.dev, #561 most downloaded on pub.dev
A convenient request router for the shelf web-framework, with support for URL-parameters, nested routers and routers generated from source annotations.
Latest stable
1.1.5
Last release 1 months ago
16 Oct 2026
Ships unpredictably
gaps range from 5 weeks to 3.5 years
Nearly every release is documented
notes for 13 of 13 stable releases
Nothing withdrawn
no release was ever pulled
8 years old
13 releases · first in 2019
Drag across the ruler to compare, or tap a release to open it.
Match parameterless routes by string comparison instead of executing their compiled pattern. A route with no <param> segments compiles to ^ plus an es
<param> segments compiles to ^ plus an$, which matches exactly one string, so the regexRouter matching with a prefix Trie filter for static path segments.HEAD request handling to not modify content-length.^3.9.0.Support analyzer: '^10.0.0'
analyzer: '^10.0.0'Your coding agent can read these notes before it upgrades. Set up the MCP server →
Require analyzer: ^8.1.1 Require build: ^4.0.0 Require build_config: ^1.2.0 Require source_gen: ^4.0.1 Require sdk: ^3.9.0
analyzer: ^8.1.1build: ^4.0.0build_config: ^1.2.0source_gen: ^4.0.1sdk: ^3.9.0Require analyzer: '>=7.4.0 <9.0.0'
analyzer: '>=7.4.0 <9.0.0'build: ^3.0.0build_config: ^1.1.0source_gen: ^3.0.0sdk: ^3.7.0Support the latest package:analyzer and package:source_gen
package:analyzer and package:source_gensdk: ^3.3.0…routeNotFound response object is technically a _breaking change_. However, it only affects scenarios where the request matches a _mounted sub-router_,…
params is deprecated in favor of Request.params adding using an extension
on Request.notFoundHandler now returns a sentinel routeNotFound response
object which causes 404 with the message 'Route not found'.routeNotFound response object will be ignored and pattern matching will
continue on additional routes/handlers.Changing the router to continue pattern matching additional routes if a matched
handler or nested router returns the sentinel routeNotFound response
object is technically a breaking change. However, it only affects scenarios
where the request matches a mounted sub-router, but does not match any route
on this sub-router. In this case, shelf_router version 1.0.0 would
immediately respond 404, without attempting to match further routes. With this
release, the behavior changes to matching additional routes until one returns
a custom 404 response object, or all routes have been matched.
This behavior is more in line with how shelf_router version 0.7.x worked,
and since many affected users consider the behavior from 1.0.0 a defect,
we decided to remedy the situation.
__Breaking__: Remove deprecated Router.handler getter. The router itself is a handler.
null in shelf 1.0.0, a router
will return a default 404 response instead.
This behavior can be overridden with the notFoundHandler constructor
parameter.Router.handler getter.
The router itself is a handler.Deprecate the Router.handler getter.
Router.mount parameter to accept a Handler.Router to be considered a Handler.Router.handler getter.Added @sealed annotation to Router and Route.
@sealed annotation to Router and Route.Always register a HEAD handler whenever a GET handler is registered. Defaulting to calling the GET handler and throwing away the body.
HEAD handler whenever a GET handler is registered.
Defaulting to calling the GET handler and throwing away the body.Use Function instead of dynamic in RouterEntry to improve typing.
Function instead of dynamic in RouterEntry to improve typing.Fixed description to fit size recommendations.
* Initial release
One column per quarter.