# Svelte Router Logo Svelte Router > Next-level routing for Svelte and Sveltekit. [REPL Demo](https://svelte.dev/playground/d273d356947e48c0822a65402fd06fac) [Full Documentation](https://svelte-router.dev) ## Features - **Always-on path and hash routing**: Simultaneous, independent and always-on routing modes. - **Multi hash routing**: Doing micro-frontends? Routing tabs or dialogs using the URL? Have as many paths as needed. - **Sveltekit support**: Add hash routing on top of Sveltekit's path routing via [@svelte-router/kit](https://github.com/WJSoftware/svelte-router-kit) - **Electron support**: Works with Electron (all routing modes) - **Reactivity-based**: All data is reactive, reducing the need for events and imperative programming. - **URL Redirection**: Use `Redirector` instances to route users from deprecated URL's to new URL's, even across routing universes. - **Dynamic Routes**: Define routes in JavaScript from any dynamic source, even fetched data. - **Fully Typed**: Built-in TypeScript, even for route parameters. **Components**: - `` - `` - `` - `` - `` - `` **Reactive Data**: - `location.url` - `location.path` - `location.hashPaths` - `location.getState()` - `RouterEngine.routes` - `RouterEngine.routeStatus` - `RouterEngine.basePath` All data is a Svelte signal. Add routes dynamically or reactively, change route conditions on the fly, add more pieces of user interface on-demand, etc. All works reactively. ### Two Library Modes Most people only need the normal or "lite" version. Use the full version to battle/counter foreign routers (micro-frontend scenarios, most likely). #### In Full Mode... - **History API interception**: Gain control over the history object to avoid external code/routers from de-synchronizing state. - **Cancellable `beforeNavigate` event**: Get notified of navigation events, and cancel when appropriate. - **`navigationCancelled` event**: Get notified whenever navigation is cancelled. ## Quickstart 1. Install the package. 2. Initialize the library. 3. Define the routes inside routers. 4. Modify/Add your navigation links. ### Install the package ```bash npm i @svelte-router/core ``` ### Initialize the Library ```typescript // In your main.ts, or somewhere BEFORE any routers are created: import { init } from '@svelte-router/core'; /* Default: - Lite mode - Implicit path routing - No router hierarchy tracing - Single hash mode - Log to console. */ init(); // Or use initFull() for full-mode. // Common case: "I just need good, old-fashioned hash routing." init({ defaultHash: true }); ``` #### Electron Variant In Electron, perform immediate navigation to clean the environment's path: ```typescript import { init, location } from '@svelte-router/core'; init(); location.goTo('/'); ``` > **⚠️ Important:** Hash routing doesn't require this extra navigation step. For applications that also run in the browser, condition the navigation to Electron only. See the [Electron page](https://svelte-router.dev/docs/electron-support) online for more details. ### Define the Routes ```svelte

Routing Demo

{#snippet children({ rp })} {/snippet} ...
``` ### Navigation Links The best practice is to render the links inside a router's hierarchy, but this is not mandatory. ```svelte ``` --- [Issues Here](https://github.com/WJSoftware/svelte-router/issues) [Questions, Polls, Show & Tell, etc. Here](https://github.com/WJSoftware/svelte-router/discussions)