natxocc/sigpro
1
1
Fork 0
Code Issues Actions Packages Projects Releases Wiki Activity

Modular router db and locale

Browse Source
This commit is contained in:
Natxo
2026-05-22 23:05:08 +02:00
parent 8481e339cc
commit eb1c81ec26
16 changed files with 143 additions and 107 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
docs/router.md
View File

@@ -17,7 +17,7 @@ router(routes: Route[]): HTMLElement
**Returns:** A `div` element (with class `"router-hook"`) that acts as the router outlet. The router automatically destroys the previous view and mounts the matched component when the hash changes.
> **Availability:** `router` and its helper methods (`router.to`, `router.back`, `router.path`, `router.params`) are exported from the SigPro module. In **ESM** you must import them (`import { router } from 'sigpro/utils'`). In the **IIFE** classic script, they are automatically available on `window`. The examples below assume the functions are already in scope.
> You must import them (`import { router } from 'sigpro/router'`). The examples below assume the functions are already in scope.
---
@@ -28,6 +28,9 @@ router(routes: Route[]): HTMLElement
Place the `router` element where you want the page content to appear. Inside the routes array, define your routes.
```javascript
// remember import router
import { router } from 'sigpro/router'
const Home = () => h1("Home Page");
const UserProfile = (params) => h1(`User ID: ${params.id}`);
const NotFound = () => h1("404 – Page not found");
@@ -189,6 +192,10 @@ mount(App, "#app");
| `router.params()` | Reactive signal of the current route parameters. |
---
# Vite Plugin: File-based Routing
The `sigproRouter` plugin for Vite automates route generation by scanning your `pages` directory. It creates a **virtual module** that you can import directly into your code, eliminating the need to maintain a manual routes array.