ui5-lib-guard-router 1.0.1 → 1.1.1

package/LICENSE

@@ -1,21 +1,21 @@
-MIT License
-
-Copyright (c) 2025 Marco
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
+MIT License
+
+Copyright (c) 2025 Marco
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -1,20 +1,20 @@
 # ui5-lib-guard-router
 
-Drop-in replacement for `sap.m.routing.Router` that intercepts navigation **before** route matching, target loading, or view creation — preventing flashes of unauthorized content and polluted browser history.
+Drop-in replacement for `sap.m.routing.Router` that intercepts navigation **before** route matching, target loading, or view creation, preventing flashes of unauthorized content and polluted browser history.
 
 > Born from [SAP/openui5#3411](https://github.com/SAP/openui5/issues/3411), an open request since 2021 for native navigation guard support in UI5.
 >
 > **Related resources**:
 >
 > - [Stack Overflow: Preventing router from navigating](https://stackoverflow.com/questions/29165700/preventing-router-from-navigating/29167292#29167292) (native NavContainer `navigate` event, sync-only, fires after route match)
-> - [Research: Native NavContainer navigate event](../../docs/research-native-router-navigate-event.md) (detailed comparison with this library)
+> - [Research: Native NavContainer navigate event](../../docs/research/native-router-navigate-event.md) (detailed comparison with this library)
 
 > [!WARNING]
-> This library is **experimental**. It is not battle-tested in production environments, and the API may change without notice. If you choose to consume it, you do so at your own risk — make sure to pin your version and review changes before upgrading.
+> This library is **experimental**. It is not battle-tested in production environments, and the API may change without notice. If you choose to consume it, you do so at your own risk. Make sure to pin your version and review changes before upgrading.
 
 ## Why
 
-UI5's router has no way to block or redirect navigation before views render. The usual workaround — scattering guard logic across `attachPatternMatched` callbacks — causes flashes of unauthorized content, polluted browser history, and scattered guard logic across controllers.
+UI5's router has no way to block or redirect navigation before views render. The usual workaround, scattering guard logic across `attachPatternMatched` callbacks, causes flashes of unauthorized content, polluted browser history, and scattered guard logic across controllers.
 
 This library solves all three by intercepting at the router level, before any route matching begins.
 
@@ -24,6 +24,90 @@ This library solves all three by intercepting at the router level, before any ro
 npm install ui5-lib-guard-router
 ```
 
+### TypeScript (optional)
+
+If your app uses TypeScript and does not already depend on the UI5 typings, install them too (`@sapui5/types` works as well):
+
+```bash
+npm install -D @openui5/types
+```
+
+Add both packages to `compilerOptions.types`:
+
+```json
+{
+	"compilerOptions": {
+		"types": ["@openui5/types", "ui5-lib-guard-router"]
+	}
+}
+```
+
+Then import types from the UI5 module path as needed:
+
+```typescript
+// Core: router interface and guard function signatures
+import type { GuardRouter, GuardFn, LeaveGuardFn } from "ui5/guard/router/types";
+
+// Guard pipeline: context passed to guards, and the result union they return
+import type { GuardContext, GuardResult } from "ui5/guard/router/types";
+
+// Advanced: object form for redirect-with-parameters and enter+leave registration
+import type { GuardRedirect, RouteGuardConfig } from "ui5/guard/router/types";
+```
+
+### Serving the library
+
+The npm package ships both pre-built distributables (`dist/`) and TypeScript sources (`src/`). There are three ways to serve the library in your app:
+
+#### Option A: Pre-built (recommended)
+
+The package includes a [UI5 build manifest](https://github.com/SAP/ui5-tooling/blob/main/rfcs/0006-local-dependency-resolution.md) (`dist/.ui5/build-manifest.json`). UI5 Tooling v4+ detects it automatically and serves the pre-built JavaScript from `dist/` with no extra configuration:
+
+```bash
+npm install ui5-lib-guard-router
+# That's it. `ui5 serve` picks up the build manifest.
+```
+
+No transpile tooling, no middleware, no additional `ui5.yaml` changes.
+
+#### Option B: Transpile from source
+
+If you prefer to serve from TypeScript sources (e.g. for debugging with source maps), install [`ui5-tooling-transpile`](https://github.com/nicholasmackey/ui5-tooling-transpile) and enable `transpileDependencies` in your app's `ui5.yaml`:
+
+```bash
+npm install -D ui5-tooling-transpile
+```
+
+```yaml
+# ui5.yaml
+server:
+    customMiddleware:
+        - name: ui5-tooling-transpile-middleware
+          afterMiddleware: compression
+          configuration:
+              transpileDependencies: true
+```
+
+This transpiles the library's `.ts` sources on the fly during `ui5 serve`.
+
+#### Option C: Static serving (workaround)
+
+If neither option works for your setup, you can mount the pre-built resources manually using [`ui5-middleware-servestatic`](https://github.com/nicholasmackey/ui5-middleware-servestatic) (or a similar community middleware) and point it at the `dist/resources` folder in `node_modules`:
+
+```bash
+npm install -D ui5-middleware-servestatic
+```
+
+```yaml
+# ui5.yaml
+server:
+    customMiddleware:
+        - name: ui5-middleware-servestatic
+          afterMiddleware: compression
+          configuration:
+              rootPath: node_modules/ui5-lib-guard-router/dist/resources
+```
+
 ## Setup
 
 **1. Add the library dependency and set the router class in your `manifest.json`:**
@@ -61,14 +145,14 @@ export default class Component extends UIComponent {
 
 	init(): void {
 		super.init();
-		const router = this.getRouter() as unknown as GuardRouter;
+		const router = this.getRouter() as GuardRouter;
 
-		// Route-specific guard — redirect when not logged in
+		// Route-specific guard: redirect when not logged in
 		router.addRouteGuard("protected", (context) => {
 			return isLoggedIn() ? true : "home";
 		});
 
-		// Global guard — runs for every navigation
+		// Global guard: runs for every navigation
 		router.addGuard((context) => {
 			if (context.toRoute === "admin" && !isAdmin()) {
 				return "home";
@@ -115,37 +199,51 @@ All methods return `this` for chaining.
 
 Every guard receives a `GuardContext` object:
 
-| Property      | Type                                               | Description                                         |
-| ------------- | -------------------------------------------------- | --------------------------------------------------- |
-| `toRoute`     | `string`                                           | Target route name (empty if no match)               |
-| `toHash`      | `string`                                           | Raw hash being navigated to                         |
-| `toArguments` | `Record<string, string \| Record<string, string>>` | Parsed route parameters                             |
-| `fromRoute`   | `string`                                           | Current route name (empty on first navigation)      |
-| `fromHash`    | `string`                                           | Current hash                                        |
-| `signal`      | `AbortSignal`                                      | Aborted when a newer navigation supersedes this one |
+| Property      | Type                                               | Description                                                       |
+| ------------- | -------------------------------------------------- | ----------------------------------------------------------------- |
+| `toRoute`     | `string`                                           | Target route name (empty if no match)                             |
+| `toHash`      | `string`                                           | Raw hash being navigated to                                       |
+| `toArguments` | `Record<string, string \| Record<string, string>>` | Parsed route parameters                                           |
+| `fromRoute`   | `string`                                           | Current route name (empty on first navigation)                    |
+| `fromHash`    | `string`                                           | Current hash                                                      |
+| `signal`      | `AbortSignal`                                      | Aborted when navigation is superseded, or on `stop()`/`destroy()` |
+
+### Return values (`GuardResult`)
+
+Enter guards return `GuardResult`, a union of four outcomes:
+
+```
+GuardResult = boolean | string | GuardRedirect
+```
 
-### Return values
+| Return                                         | Type            | When to use                                             | Effect                                          |
+| ---------------------------------------------- | --------------- | ------------------------------------------------------- | ----------------------------------------------- |
+| `true`                                         | `boolean`       | Guard condition passes                                  | Allow navigation                                |
+| `false`                                        | `boolean`       | Guard condition fails, no specific destination          | Block (stay on current route, no history entry) |
+| `"routeName"`                                  | `string`        | Redirect to a fixed route (no parameters needed)        | Redirect to named route (replaces history)      |
+| `{ route, parameters?, componentTargetInfo? }` | `GuardRedirect` | Redirect and pass route parameters or component targets | Redirect with parameters (replaces history)     |
 
-**Enter guards** (`addGuard`, `addRouteGuard`):
+`GuardRedirect` is the object form of a redirect. Use it when you need to pass route parameters (`parameters`) or nested component targets (`componentTargetInfo`). For simple redirects without parameters, the string shorthand (`return "home"`) is equivalent and shorter.
 
-| Return                                         | Effect                                          |
-| ---------------------------------------------- | ----------------------------------------------- |
-| `true`                                         | Allow navigation                                |
-| `false`                                        | Block (stay on current route, no history entry) |
-| `"routeName"`                                  | Redirect to named route (replaces history)      |
-| `{ route, parameters?, componentTargetInfo? }` | Redirect with route parameters                  |
-| anything else (`null`, `undefined`)            | Treated as block                                |
+Any other value (`null`, `undefined`, `0`, etc.) is treated as a block. Only strict `true` allows navigation -- there is no truthy coercion.
 
-Only strict `true` allows navigation — no truthy coercion.
+On first load, blocking a non-empty hash restores `""` and continues with the app's default route. Blocking the default route itself stays blocked. If you need a specific denied-first-load destination such as `login`, return a redirect instead of `false`.
 
-**Leave guards** (`addLeaveGuard`):
+**Leave guards** (`addLeaveGuard`) return `boolean` only:
 
 | Return                            | Effect                          |
 | --------------------------------- | ------------------------------- |
 | `true`                            | Allow leaving the current route |
 | `false` (or any non-`true` value) | Block                           |
 
-Leave guards cannot redirect. For redirection logic, use enter guards on the target route.
+Leave guards answer "can I leave?" and cannot redirect. For redirection logic, use enter guards on the target route.
+
+### Lifecycle
+
+| Method      | Behavior                                                                                                                                                                                      |
+| ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `stop()`    | Cancels pending async guards (aborts the `AbortSignal`), resets guard state. A subsequent `initialize()` re-parses the current hash and fires `routeMatched`, matching native router behavior |
+| `destroy()` | Clears all registered guards (global, enter, leave), cancels pending async guards, then calls `super.destroy()`                                                                               |
 
 ### Execution order
 
@@ -159,19 +257,23 @@ Leave guards cannot redirect. For redirection logic, use enter guards on the tar
 ### Async guard with AbortSignal
 
 ```typescript
-router.addRouteGuard("dashboard", async (context) => {
+import type { GuardContext, GuardResult } from "ui5/guard/router/types";
+
+router.addRouteGuard("dashboard", async (context: GuardContext): Promise<GuardResult> => {
 	const res = await fetch(`/api/access/${context.toRoute}`, {
-		signal: context.signal,
+		signal: context.signal, // cancelled when a newer navigation supersedes this one
 	});
 	const { allowed } = await res.json();
 	return allowed ? true : "forbidden";
 });
 ```
 
-### Redirect with parameters
+### Redirect with parameters (GuardRedirect)
 
 ```typescript
-router.addGuard((context) => {
+import type { GuardRedirect } from "ui5/guard/router/types";
+
+router.addGuard((context): GuardRedirect | true => {
 	if (context.toRoute === "old-detail") {
 		return {
 			route: "detail",
@@ -202,13 +304,18 @@ export function createDirtyFormGuard(formModel: JSONModel): LeaveGuardFn {
 }
 ```
 
-### Object form (enter + leave)
+### Object form with RouteGuardConfig
 
 ```typescript
-router.addRouteGuard("editOrder", {
+import type { RouteGuardConfig } from "ui5/guard/router/types";
+
+const orderGuards: RouteGuardConfig = {
 	beforeEnter: createAuthGuard(authModel),
 	beforeLeave: createDirtyFormGuard(formModel),
-});
+};
+
+router.addRouteGuard("editOrder", orderGuards);
+// later: router.removeRouteGuard("editOrder", orderGuards);
 ```
 
 ### Dynamic guard registration
@@ -239,13 +346,13 @@ export default class EditOrderController extends Controller {
 		const formModel = new JSONModel({ isDirty: false });
 		this.getView()!.setModel(formModel, "form");
 
-		const router = (this.getOwnerComponent() as UIComponent).getRouter() as unknown as GuardRouter;
+		const router = UIComponent.getRouterFor(this) as GuardRouter;
 		this._leaveGuard = createDirtyFormGuard(formModel);
 		router.addLeaveGuard("editOrder", this._leaveGuard);
 	}
 
 	onExit(): void {
-		const router = (this.getOwnerComponent() as UIComponent).getRouter() as unknown as GuardRouter;
+		const router = UIComponent.getRouterFor(this) as GuardRouter;
 		router.removeLeaveGuard("editOrder", this._leaveGuard);
 	}
 }
@@ -278,10 +385,10 @@ sap.ushell.Container.setDirtyFlag(false); // clear after save
 
 ```typescript
 const dirtyProvider = (navigationContext) => {
-	if (navigationContext?.isCrossAppNavigation) {
-		return formModel.getProperty("/isDirty");
+	if (navigationContext?.isCrossAppNavigation === false) {
+		return false; // let in-app routing handle it
 	}
-	return false; // let in-app routing handle it
+	return formModel.getProperty("/isDirty") === true;
 };
 sap.ushell.Container.registerDirtyStateProvider(dirtyProvider);
 
@@ -291,12 +398,34 @@ sap.ushell.Container.deregisterDirtyStateProvider(dirtyProvider);
 
 > **Note**: `getDirtyFlag()` is deprecated since UI5 1.120. FLP internally uses `getDirtyFlagsAsync()` (private) which combines the flag with all registered providers. The synchronous `getDirtyFlag()` still works but should not be relied upon in new code.
 
-**How the two approaches complement each other**: FLP's data loss protection operates at the shell navigation filter level, intercepting navigation _before_ the hash change reaches your app's router. Leave guards operate _inside_ your app's router, intercepting route-to-route navigation. For complete coverage:
+#### Combining leave guards with FLP dirty-state protection
+
+When you use both a route leave guard and `registerDirtyStateProvider`, the two handle separate scopes and do not need to coordinate in application code:
+
+- **Leave guard** protects **in-app** navigation (route to route within your app)
+- **Dirty-state provider** protects **cross-app** navigation (shell home, other tiles, browser close)
+
+In production FLP, `ShellNavigationHashChanger` intercepts cross-app navigation **before** it reaches the app router, so the leave guard never runs for cross-app hashes. The two mechanisms never overlap:
+
+```typescript
+// 1. Leave guard: blocks in-app navigation when dirty
+router.addRouteGuard("editOrder", {
+	beforeLeave: () => formModel.getProperty("/isDirty") !== true,
+});
+
+// 2. Dirty-state provider: tells FLP about unsaved changes for cross-app
+const dirtyProvider = (navigationContext) => {
+	if (navigationContext?.isCrossAppNavigation === false) {
+		return false; // in-app navigation handled by leave guard
+	}
+	return formModel.getProperty("/isDirty") === true;
+};
+sap.ushell.Container.registerDirtyStateProvider(dirtyProvider);
+```
 
-- Use **leave guards** for in-app route changes (e.g., navigating from an edit form to a list within your app)
-- Use **`setDirtyFlag`** or **`registerDirtyStateProvider`** for FLP-level navigation (cross-app, browser close, home button)
+No `toRoute` check or FLP detection is needed in the leave guard. Cross-app navigation via `toExternal()` operates at the shell level in both production and the FLP sandbox, so the leave guard never runs for cross-app hashes. The leave guard protects in-app route changes; the FLP dirty-state provider protects cross-app navigation, browser close, and the shell home button.
 
-See the [FLP Dirty State Research](../../docs/research-flp-dirty-state.md) for a detailed analysis of the FLP internals.
+See the [FLP Dirty State Research](../../docs/research/flp-dirty-state.md) for a detailed analysis of the FLP internals.
 
 ## Limitations
 
@@ -373,10 +502,16 @@ This follows the same pattern as [TanStack Router's `pendingComponent`](https://
 ## Compatibility
 
 > [!IMPORTANT]
-> **Minimum UI5 version: 1.118**
+> **Shipped UI5 baseline: 1.144.0**
 >
-> The library uses [`sap.ui.core.Lib`](https://sdk.openui5.org/api/sap.ui.core.Lib) for library initialization, which was introduced in **UI5 1.118**. The Router itself only depends on APIs available since 1.75 (notably [`getRouteInfoByHash`](https://sdk.openui5.org/api/sap.ui.core.routing.Router%23methods/getRouteInfoByHash)), but the library packaging sets the effective floor. Developed and tested against OpenUI5 1.144.0.
+> The published package declares `minUI5Version: 1.144.0`, and the full CI suite runs on that shipped baseline. In addition, CI runs the library QUnit suite against OpenUI5 `1.118.0` as a compatibility lane for the core router implementation. That extra lane does not change the published manifest baseline, but it provides a concrete verification signal for consumers evaluating older runtimes.
+
+If you maintain an app on an older UI5 stack and want to validate locally, run the dedicated compatibility check from the monorepo root:
+
+```bash
+npm run test:qunit:compat:118
+```
 
 ## License
 
-[MIT](../../LICENSE)
+[MIT](LICENSE)

package/dist/.ui5/build-manifest.json

@@ -0,0 +1,75 @@
+{
+	"project": {
+		"specVersion": "4.0",
+		"type": "library",
+		"metadata": {
+			"name": "ui5.guard.router"
+		},
+		"resources": {
+			"configuration": {
+				"paths": {
+					"src": "resources",
+					"test": "test-resources"
+				}
+			}
+		}
+	},
+	"buildManifest": {
+		"manifestVersion": "0.2",
+		"timestamp": "2026-03-16T11:10:25.198Z",
+		"versions": {
+			"builderVersion": "4.1.4",
+			"projectVersion": "4.0.13",
+			"fsVersion": "4.0.5"
+		},
+		"buildConfig": {
+			"selfContained": false,
+			"cssVariables": false,
+			"jsdoc": false,
+			"createBuildManifest": true,
+			"outputStyle": "Default",
+			"includedTasks": [],
+			"excludedTasks": []
+		},
+		"version": "1.1.1",
+		"namespace": "ui5/guard/router",
+		"tags": {
+			"/resources/ui5/guard/router/library-dbg.js": {
+				"ui5:IsDebugVariant": true
+			},
+			"/resources/ui5/guard/router/library-dbg.js.map": {
+				"ui5:IsDebugVariant": true
+			},
+			"/resources/ui5/guard/router/library.js": {
+				"ui5:HasDebugVariant": true
+			},
+			"/resources/ui5/guard/router/library.js.map": {
+				"ui5:HasDebugVariant": true
+			},
+			"/resources/ui5/guard/router/Router-dbg.js": {
+				"ui5:IsDebugVariant": true
+			},
+			"/resources/ui5/guard/router/Router-dbg.js.map": {
+				"ui5:IsDebugVariant": true
+			},
+			"/resources/ui5/guard/router/Router.js": {
+				"ui5:HasDebugVariant": true
+			},
+			"/resources/ui5/guard/router/Router.js.map": {
+				"ui5:HasDebugVariant": true
+			},
+			"/resources/ui5/guard/router/types-dbg.js": {
+				"ui5:IsDebugVariant": true
+			},
+			"/resources/ui5/guard/router/types-dbg.js.map": {
+				"ui5:IsDebugVariant": true
+			},
+			"/resources/ui5/guard/router/types.js": {
+				"ui5:HasDebugVariant": true
+			},
+			"/resources/ui5/guard/router/types.js.map": {
+				"ui5:HasDebugVariant": true
+			}
+		}
+	}
+}

package/dist/index.d.ts

@@ -1,27 +1,33 @@
 // Generated with TypeScript 5.7.3 / OpenUI5 1.144.0 using:
 //   - yargs-parser@20.2.9
 //   - typescript@5.7.3
+//   - url@0.11.4
 //   - string_decoder@1.3.0
-//   - buffer@6.0.3
+//   - punycode@1.4.1
 //   - events@3.3.0
-//   - undici-types@6.21.0
+//   - buffer@6.0.3
+//   - undici-types@7.18.2
 //   - @types/yauzl@2.10.3
 //   - @types/yargs-parser@21.0.3
 //   - @types/yargs@17.0.35
 //   - @types/ws@8.18.1
 //   - @types/which@2.0.2
+//   - @types/three@0.125.3
 //   - @types/stack-utils@2.0.3
 //   - @types/sizzle@2.3.10
 //   - @types/sinonjs__fake-timers@8.1.5
+//   - @types/shimmer@1.2.0
 //   - @types/qunit@2.5.4
+//   - @types/offscreencanvas@2019.6.4
 //   - @types/normalize-package-data@2.4.4
-//   - @types/node@20.19.32
+//   - @types/node@25.5.0
 //   - @types/mocha@10.0.10
+//   - @types/minimatch@3.0.5
 //   - @types/jquery@3.5.13
 //   - @types/istanbul-reports@3.0.4
 //   - @types/istanbul-lib-report@3.0.3
 //   - @types/istanbul-lib-coverage@2.0.6
 //   - @types/qunit@2.19.13
-/// <reference path="./resources/ui5/guard/router/library.d.ts"/>
 /// <reference path="./resources/ui5/guard/router/types.d.ts"/>
+/// <reference path="./resources/ui5/guard/router/library.d.ts"/>
 /// <reference path="./resources/ui5/guard/router/Router.d.ts"/>

package/dist/resources/ui5/guard/router/.library

@@ -1,17 +1,17 @@
-<?xml version="1.0" encoding="UTF-8" ?>
-<library xmlns="http://www.sap.com/sap.ui.library.xsd">
-	<name>ui5.guard.router</name>
-	<vendor>Marco</vendor>
-	<version>1.0.1</version>
-	<copyright></copyright>
-	<title>UI5 Router extension with async navigation guards</title>
-	<documentation>Extends sap.m.routing.Router with async navigation guards, running before route matching begins.</documentation>
-	<dependencies>
-		<dependency>
-			<libraryName>sap.ui.core</libraryName>
-		</dependency>
-		<dependency>
-			<libraryName>sap.m</libraryName>
-		</dependency>
-	</dependencies>
-</library>
+<?xml version="1.0" encoding="UTF-8" ?>
+<library xmlns="http://www.sap.com/sap.ui.library.xsd">
+	<name>ui5.guard.router</name>
+	<vendor>Marco</vendor>
+	<version>1.1.1</version>
+	<copyright></copyright>
+	<title>UI5 Router extension with async navigation guards</title>
+	<documentation>Extends sap.m.routing.Router with async navigation guards, running before route matching begins.</documentation>
+	<dependencies>
+		<dependency>
+			<libraryName>sap.ui.core</libraryName>
+		</dependency>
+		<dependency>
+			<libraryName>sap.m</libraryName>
+		</dependency>
+	</dependencies>
+</library>