@owlmeans/web-router 0.1.18-rc.11 → 0.1.18-rc.13

package/agent-meta/manifest.json

@@ -1,8 +1,8 @@
 {
   "schemaVersion": 2,
   "package": "@owlmeans/web-router",
-  "version": "0.1.18-rc.8",
-  "generatedAt": "2026-08-27T16:32:18.508Z",
+  "version": "0.1.18-rc.13",
+  "generatedAt": "2026-09-01T17:39:40.767Z",
   "canonicalRepo": "https://github.com/owlmeans/common",
   "entries": [
     {

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

@@ -8,12 +8,12 @@ user-invocable: false
 # @owlmeans/web-router
 
 **Layer:** Web (React), build level L2
-**Install:** `"@owlmeans/web-router": "^0.1.18-rc.8"` in `dependencies`
+**Install:** `"@owlmeans/web-router": "^0.1.18-rc.13"` 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
 
@@ -35,8 +35,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/build/service.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"service.d.ts","sourceRoot":"","sources":["../src/service.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,WAAW,EAAE,YAAY,EAAE,MAAM,mBAAmB,CAAA;AAClE,OAAO,KAAK,EAAE,aAAa,EAAE,MAAM,kBAAkB,CAAA;AAIrD;;;GAGG;AACH,eAAO,MAAM,oBAAoB,QAAO,aAIvC,CAAA;AAED;;;;GAIG;AACH,eAAO,MAAM,eAAe,GAAI,CAAC,SAAS,WAAW,EAAE,CAAC,SAAS,YAAY,CAAC,CAAC,CAAC,OAAO,CAAC,KAAG,CAI1F,CAAA"}
+{"version":3,"file":"service.d.ts","sourceRoot":"","sources":["../src/service.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,WAAW,EAAE,YAAY,EAAE,MAAM,mBAAmB,CAAA;AAClE,OAAO,KAAK,EAAE,aAAa,EAAE,MAAM,kBAAkB,CAAA;AAIrD;;;GAGG;AACH,eAAO,MAAM,oBAAoB,QAAO,aAIvC,CAAA;AAED;;;;GAIG;AACH,eAAO,MAAM,eAAe,GAAI,CAAC,SAAS,WAAW,EAAE,CAAC,SAAS,YAAY,CAAC,CAAC,CAAC,EAAE,KAAK,CAAC,KAAG,CAI1F,CAAA"}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@owlmeans/web-router",
-  "version": "0.1.18-rc.11",
+  "version": "0.1.18-rc.13",
   "license": "MIT",
   "type": "module",
   "scripts": {
@@ -26,7 +26,7 @@
   },
   "devDependencies": {
     "@owlmeans/dep-config": "workspace:*",
-    "@owlmeans/test-ui": "^0.1.18-rc.11",
+    "@owlmeans/test-ui": "^0.1.18-rc.14",
     "@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.6",
-    "@owlmeans/router": "^0.1.18-rc.6"
+    "@owlmeans/context": "^0.1.18-rc.7",
+    "@owlmeans/router": "^0.1.18-rc.7"
   },
   "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 }] }
 ]