NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
pub.dev · #2010 most downloaded on pub.dev
A routing component for jaspr.
Last release 2 months ago
04 Aug 2026
Release timing varies
gaps range from 9 days to 4 months
Nearly every release is documented
notes for 27 of 27 stable releases
Nothing withdrawn
no release was ever pulled
4 years old
30 releases · first in 2022
One column per quarter.
The following packages have been updated: jaspr_test : 0.23.2 -> 0.23.3 jaspr : 0.23.2 -> 0.23.3 jaspr_builder : 0.23.2 -> 0.23.3 jaspr_router : 0.8.3
The following packages have been updated:
jaspr_test : 0.23.2 -> 0.23.3
jaspr : 0.23.2 -> 0.23.3
jaspr_builder : 0.23.2 -> 0.23.3
jaspr_router : 0.8.3 -> 0.9.0
jaspr_cli : 0.23.2 -> 0.23.3
jaspr_content : 0.5.3+1 -> 0.5.4
dart_quotes : 0.1.12 -> 0.1.13 (No Changelog)
dart_quotes_server : 0.1.12 -> 0.1.13 (No Changelog)
fluttercon : 0.0.13 -> 0.0.14 (No Changelog)
website : 0.1.8 -> 0.1.9 (No Changelog)
RouteSettings.priority nullable and default to null instead of 0.5, so the sitemap priority tag can be omitted (consistent with changeFreq).dispose() to the HistoryManager interface.RouterState.dispose() to cancel onPopState subscriptions when the router is unmounted.Fixed routing and redirect bug to respect the configuration by prepending basePath on client history operations, server redirect headers, and Link hre
<base href="..."> configuration by prepending basePath on client history operations, server redirect headers, and Link hrefs.- jaspr upgraded to 0.23.0
jaspr upgraded to 0.23.0- jaspr upgraded to 0.22.0
jaspr upgraded to 0.22.0Nothing published for this version
Using a redirect function on Router or Route while rendering on the server will now trigger a HTTP redirect (302) instead of rendering the target page
redirect function on Router or Route while rendering on the server will now trigger a HTTP redirect (302) instead of rendering the target page.- jaspr upgraded to 0.21.1 - jaspr_test upgraded to 0.21.1
jaspr upgraded to 0.21.1jaspr_test upgraded to 0.21.1- jaspr upgraded to 0.21.0 - jaspr_test upgraded to 0.21.0
jaspr upgraded to 0.21.0jaspr_test upgraded to 0.21.0Nothing published for this version
Nothing published for this version
- jaspr upgraded to 0.20.0
jaspr upgraded to 0.20.0Added settings parameter to Route for specifying sitemap settings like priority and changefreq.
settings parameter to Route for specifying sitemap settings like priority and changefreq.Fixed bug with router redirects.
- jaspr upgraded to 0.18.0
jaspr upgraded to 0.18.0- Update logo and website links.
- jaspr upgraded to 0.17.0
jaspr upgraded to 0.17.0BREAKING Migrate to package:web.
package:web.- jaspr upgraded to 0.15.0
jaspr upgraded to 0.15.0Changed the signature of the Link component, children is now a named parameter.
Link component, children is now a named parameter.The title of the browser tab will no be properly set to the title of the current route.
title of the current route.Fixed issue where replaceNamed from GoRouterHelper was not passing parameters correctly.
replaceNamed from GoRouterHelper was not passing parameters correctly.Added Link component to simplify router-aware navigation.
Added Link component to simplify router-aware navigation.
The Link component lets the user navigate to another route by clicking or tapping on it. It uses client-side routing
if possible and fall back to the default browser navigation if no Router component is present in the tree. It will render
an accessible <a> element with a valid href, which means that things like right-clicking a Link work as you'd expect.
Fixed redirects on initial load.
Fixed proper handling of <base> path.
- jaspr upgraded to 0.10.0
jaspr upgraded to 0.10.0Added *Static Site Generation* support. Pages are automatically generated for each route.
Added Static Site Generation support. Pages are automatically generated for each route.
Fixed bug where Router.of(context).matchList.title always returned null.
- jaspr upgraded to 0.8.0
jaspr upgraded to 0.8.0- jaspr upgraded to 0.7.0
jaspr upgraded to 0.7.0- jaspr upgraded to 0.6.0
jaspr upgraded to 0.6.0BREAKING Complete overhaul of the router package.
BREAKING Complete overhaul of the router package.
The router implementation is mainly adapted from the go_router package for Flutter.
Routing works by providing a set of routes to the router component. You can choose between a normal
Route and a ShellRoute. A ShellRoute acts as a layout wrapper around the child routes.
Each Route takes a path which can contain parameters like '/users/:userId'.
Both Route and ShellRoute have a .lazy variant used for lazy-loading parts of the application.
Router(routes: [
// simple routes
Route(path: '/', builder: (context, state) => HomePage()),
Route(path: '/about', builder: (context, state) => AboutPage()),
// route with a path parameter
Route(path: '/users/:userId', builder: (context, state) => UserPage(id: state.pathParameters['userId'])),
// nested routes
Route(path: '/base', builder: (context, state) => BasePage(), routes: [
// full location will be '/base/details'
Route(path: 'details', builder: (context, state) => DetailsPage()),
]),
// shell route
ShellRoute(
builder: (context, state, child) => CustomLayout(child: child),
routes: [
Route(path: '/dashboard', builder: (context, state) => DashboardPage()),
]
),
// lazy loaded route
// this assumes a deferred import like "import 'posts.dart' deferred as posts;"
Route.lazy(path: '/posts', builder: (context, state) => posts.Posts(), load: posts.loadLibrary),
// lazy loaded shell route
ShellRoute.lazy(
builder: (context, state, child) => CustomLayout(child: child),
load: () => someAsyncTask(),
routes: [
Route(path: '/data', builder: (context, state) => DataPage()),
]
)
]);
While the router docs are work in progress, you can refer to the go_router docs for some references (don't expect everything to work exactly the same, but the core concepts are similar).
- jaspr upgraded to 0.4.0
jaspr upgraded to 0.4.0- Initial version.
Your coding agent can read these notes before it upgrades. Set up the MCP server →