Companion Packages
lit-ui-router is the core package. Companion packages layer optional integrations on top of it — each is published and versioned independently and depends on the core only as a peer, so you add exactly the ones you need and nothing you don't.
Published
| Package | Version | What it is |
|---|---|---|
| eslint-plugin-lit-ui-router | ESLint rules that understand the router's directives: six rules covering hrefless anchors, inert hrefs, misplaced directives, and each of the three ways a link goes active without saying so to assistive technology. | |
| lit-ui-router-effect | Effect bindings: a SubscriptionRef of the route and ref-following Lit controllers that keep components in sync with router state. | |
| lit-ui-router-mobx | MobX bindings: an observable RouterStore and reaction-based Lit controllers that keep components in sync with router state. | |
| lit-ui-router-signals | TC39 Signals bindings: watcher-based Lit controllers over ui-router-signals that keep components in sync with router state. | |
| lit-ui-router-ssr | Static prerendering: a ui-router-server mount table in, an emitted site out — one html file per shell verdict, a host rules file for the redirects. | |
| ui-router-effect | Effect for UI-Router: a framework-agnostic SubscriptionRef of the router's current state, with no Lit dependency. | |
| ui-router-navigation-location-plugin | A location plugin that manages URLs with the modern Navigation API and exposes the router in navigation events. | |
| ui-router-server | Server-side routing verdicts: honest 404/302/200 HTTP for static SPAs, run at the edge with the client's own route table. | |
| ui-router-signals | TC39 Signals for UI-Router: a framework-agnostic signal mirror of the router's current state, with no Lit dependency. |
Each package page has its own install snippet, guide, and — where the package has a runtime API — its own reference.
The Effect and Signals bindings each come as two packages: a framework-agnostic one for @uirouter/core, and a Lit one for lit-ui-router. The Effect and Signals overviews say which to install.
eslint-plugin-lit-ui-router is the odd one out: it ships lint rules rather than runtime code, so its only peer is eslint rather than the router itself. Its 1.0 line is stable, and its semver policy treats any tightening of recommended as a major.
ui-router-server is still an early 0.x line: it ships, this site's own Worker runs it in production, and its API can still move in a minor. The package page, the Server-Side Routing guide, and the sample app cover what it answers.
lit-ui-router-ssr builds on those verdicts: it renders each shell verdict into a static html file with the router handed to @lit-labs/ssr.