npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@lwce/router

v1.0.0

Published

A LWC router that supports server-side rendering

Downloads

28

Readme

@lwce/router

A lightning web component for building declarative routing within single-page applications.

Usage

  1. Install: npm install --save @lwce/router
  2. Add {"npm": "@lwce/router"} to your lwc.config.json for module resolution. See example

Note: it is highly recommended that the synthetic-shadow be used. Currently declarative routing is impossible with the native shadow dom, because slotted elements are always rendered (whether active or not).

API

lwce-router

The primary component which must wrap all other components that have routing applied.

Props:

base: The base URL for all locations. If your app is served from a sub-directory on your server, you’ll want to set this to the sub-directory. A properly formatted basename should have a leading slash, but no trailing slash.

Example:

<lwce-router base="/my-app">
  ...
</lwce-router>

lwce-route

Defines a route who's content will be rendered when the URL is active

Props:

children: Whatever HTML is passed within the slot will only be rendered if the URL is active.

path: Any valid URL path or array of paths that path-to-regexp@^1.7.0 understands.

strict: When true, a path that has a trailing slash will only match a location.pathname with a trailing slash

exact: When true, will only match if the path matches the location.pathname exactly

sensitive: When true, will match if the path is case sensitive.

default: When true, will match if no other paths are matched. Use for 404 pages.

Example:

<lwce-route path="/products/:productId">
  <my-product></my-product>
</lwce-route>

lwce-link

Define a link to navigate between your routes

Props:

title: The accessible text representing your link

href: A string representation of your destination. This can be a relative path.

class-name: Set a class to style your link

Example:

<lwce-link class-name="styled-link" path="/products/1234" title="Product details">
  Product details
</lwce-link>

routeParams

Use the routeParams wire adapter to access URL parameters

Example:

import { LightningElement, api, wire } from 'lwc';
import { routeParams } from '@lwce/router';

export default class Link extends LightningElement {
  @wire(routeParams) params;
}

And usage within the template:

<template>
  <h1>Product: {params.productId}</h1>
</template>

history

Use the history wire adapter to imperatively change routes.

Example:

import { LightningElement, api, wire } from 'lwc';
import { history } from '@lwce/router';

export default class Link extends LightningElement {
  @wire(history) history;

  onClickHandler(e) {
    this.history.push('/settings');
  }
}