@owlmeans/web-router 0.1.18-rc.4 → 0.1.18-rc.41

package/README.md

@@ -14,7 +14,7 @@ third-party router — react-router is a separate opt-in plugin,
 ## Installation
 
 ```bash
-bun add @owlmeans/web-router
+bun add @owlmeans/web-router@^0.1.18-rc.41
 ```
 
 ## Usage
@@ -50,7 +50,7 @@ This package ships embedded agent skills under `agent-meta/`. After installing y
 your project's skill store (`.agents/skills/`):
 
 ```sh
-npx @owlmeans/agent-skills
+npx @owlmeans/agent-skills@^0.1.18-rc.40
 ```
 
 The embedded files are version-matched to this package release. Do not edit them

package/agent-meta/manifest.json

@@ -1,8 +1,8 @@
 {
   "schemaVersion": 2,
   "package": "@owlmeans/web-router",
-  "version": "0.1.18-rc.0",
-  "generatedAt": "2026-08-16T22:20:50.515Z",
+  "version": "0.1.18-rc.41",
+  "generatedAt": "2026-09-25T21:19:38.001Z",
   "canonicalRepo": "https://github.com/owlmeans/common",
   "entries": [
     {

package/agent-meta/skills/web-router/SKILL.md

@@ -8,19 +8,20 @@ user-invocable: false
 # @owlmeans/web-router
 
 **Layer:** Web (React), build level L2
-**Install:** `"@owlmeans/web-router": "^0.1.18-rc.0"` in `dependencies`
+**Install:** `"@owlmeans/web-router": "^0.1.18-rc.41"` in `dependencies`
 
-As of the pluggable-routing rework this package **is the default OwlMeans in-browser router** — a
-minimal, react-router-free implementation of standard URL routing over the browser History API. It
-registers itself as a `RouterPlugin` on the `@owlmeans/router` host. (react-router now lives in the
-separate opt-in `@owlmeans/web-router-react-router` package.)
+This package **is the default OwlMeans in-browser router** — a minimal, react-router-free
+implementation of standard URL routing over the browser History API. It registers itself as a
+`RouterPlugin` on the `@owlmeans/router` host. (react-router is the separate opt-in
+`@owlmeans/web-router-react-router` package.)
 
 ## Key Exports
 
 | Export | Description |
 |--------|-------------|
 | `appendWebRouter(ctx)` | Register the OwlMeans browser plugin on a context's router host (idempotent via `ensureRouterService`). Called transparently by `@owlmeans/web-client`. |
-| `makeBrowserRouterPlugin()` | The `RouterPlugin` itself (alias `owlmeans-browser-router`, priority 0). |
+| `makeBrowserRouterPlugin()` | The `RouterPlugin` itself (alias `BROWSER_ROUTER`, priority 0). |
+| `BROWSER_ROUTER` | The plugin's alias string, `'owlmeans-browser-router'` — name the constant rather than the literal when selecting or overriding the plugin. |
 | `makeWebRouterService()` | Back-compat: a host pre-loaded with the browser plugin. |
 | `BrowserRouterProvider`, `Outlet` | React provider/outlet components. |
 | `RouteChain` | Renders the matched chain from a given depth, skipping `Component`-less matches (used by the provider and `Outlet`). |
@@ -35,8 +36,8 @@ separate opt-in `@owlmeans/web-router-react-router` package.)
   chain via `RouteChain`; `<Outlet/>` renders the next-deeper match (depth tracked via context).
   Composes unchanged with the `@owlmeans/client` route renderer (parent components emit `<Outlet/>`).
 - **Component-less matches are pass-through** — exactly like react-router's implicit `<Outlet/>` for
-  element-less routes. `@owlmeans/client` emits `RouteObject`s with no `Component` for modules that
-  have no handler (grouping modules such as `client-authentication` →
+  element-less routes. `@owlmeans/client` emits `RouteObject`s with no `Component` for entrypoints
+  that have no handler (grouping entrypoints such as `client-authentication` →
   `client-authentication:authentication`), so rendering only the exact node at a depth would blank
   the whole subtree. `RouteChain` walks down to the first match that has a `Component`, and the
   `OutletContext` depth it publishes is that match's depth, so nested outlets stay aligned.

package/build/browser/chain.d.ts

@@ -4,11 +4,11 @@ import type { FC } from 'react';
  *
  * A matched route that carries no `Component` is a **pass-through**: it renders
  * the next-deeper match, exactly like react-router's implicit `<Outlet/>` for
- * element-less routes. OwlMeans module trees depend on this — grouping modules
- * (e.g. `client-authentication` → `client-authentication:authentication`) have
- * no handler, so `@owlmeans/client` emits `RouteObject`s without a `Component`
+ * element-less routes. OwlMeans entrypoint trees depend on this — grouping
+ * entrypoints (e.g. `client-authentication` → `client-authentication:authentication`)
+ * have no handler, so `@owlmeans/client` emits `RouteObject`s without a `Component`
  * for them. Rendering only the exact node at `depth` would leave the whole
- * subtree blank whenever a group sits above the screen module.
+ * subtree blank whenever a group sits above the screen entrypoint.
  */
 export declare const RouteChain: FC<{
     depth: number;

package/build/browser/chain.js

@@ -5,11 +5,11 @@ import { RouterStateContext, OutletContext } from './context.js';
  *
  * A matched route that carries no `Component` is a **pass-through**: it renders
  * the next-deeper match, exactly like react-router's implicit `<Outlet/>` for
- * element-less routes. OwlMeans module trees depend on this — grouping modules
- * (e.g. `client-authentication` → `client-authentication:authentication`) have
- * no handler, so `@owlmeans/client` emits `RouteObject`s without a `Component`
+ * element-less routes. OwlMeans entrypoint trees depend on this — grouping
+ * entrypoints (e.g. `client-authentication` → `client-authentication:authentication`)
+ * have no handler, so `@owlmeans/client` emits `RouteObject`s without a `Component`
  * for them. Rendering only the exact node at `depth` would leave the whole
- * subtree blank whenever a group sits above the screen module.
+ * subtree blank whenever a group sits above the screen entrypoint.
  */
 export const RouteChain = ({ depth }) => {
     const state = useContext(RouterStateContext);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@owlmeans/web-router",
-  "version": "0.1.18-rc.4",
+  "version": "0.1.18-rc.41",
   "license": "MIT",
   "type": "module",
   "scripts": {
@@ -26,7 +26,7 @@
   },
   "devDependencies": {
     "@owlmeans/dep-config": "workspace:*",
-    "@owlmeans/test-ui": "^0.1.18-rc.4",
+    "@owlmeans/test-ui": "^0.1.18-rc.41",
     "@types/node": "^26.1.0",
     "@types/react": "^19.2.17",
     "@vitejs/plugin-react": "^6.0.3",
@@ -38,8 +38,8 @@
     "vite": "^8.1.2"
   },
   "dependencies": {
-    "@owlmeans/context": "^0.1.18-rc.4",
-    "@owlmeans/router": "^0.1.18-rc.4"
+    "@owlmeans/context": "^0.1.18-rc.32",
+    "@owlmeans/router": "^0.1.18-rc.31"
   },
   "publishConfig": {
     "access": "public"

package/src/browser/chain.tsx

@@ -7,11 +7,11 @@ import { RouterStateContext, OutletContext } from './context.js'
  *
  * A matched route that carries no `Component` is a **pass-through**: it renders
  * the next-deeper match, exactly like react-router's implicit `<Outlet/>` for
- * element-less routes. OwlMeans module trees depend on this — grouping modules
- * (e.g. `client-authentication` → `client-authentication:authentication`) have
- * no handler, so `@owlmeans/client` emits `RouteObject`s without a `Component`
+ * element-less routes. OwlMeans entrypoint trees depend on this — grouping
+ * entrypoints (e.g. `client-authentication` → `client-authentication:authentication`)
+ * have no handler, so `@owlmeans/client` emits `RouteObject`s without a `Component`
  * for them. Rendering only the exact node at `depth` would leave the whole
- * subtree blank whenever a group sits above the screen module.
+ * subtree blank whenever a group sits above the screen entrypoint.
  */
 export const RouteChain: FC<{ depth: number }> = ({ depth }) => {
   const state = useContext(RouterStateContext)

package/tests/harness/mount.tsx

@@ -49,7 +49,7 @@ const routes: RouteObject[] = [
     ]
   },
   // component-less grouping node at the very top of the chain — this is the shape
-  // `@owlmeans/client` emits for modules without a handler (e.g. `client-authentication`)
+  // `@owlmeans/client` emits for entrypoints without a handler (e.g. `client-authentication`)
   { path: 'group', children: [{ path: 'leaf', Component: Leaf }] }
 ]