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

@smore/trailmap

v0.1.1

Published

Simple component that generates @stencil/router routes, mapping a url to a content path

Downloads

2

Readme

Built With Stencil

TrailMap

TrailMap is a simple Functional Component to be used with @stencil/router within Stencil apps. It simplifies the process of grouping a set of routes and mapping URLs to a path where content can be found.

Getting Started

npm install @smore/trailmap

Add TrailMap to your <stencil-route-switch> definiton (most likely in app-root.) Under the hood, it will generate the necessary <stencil-route> and <stencil-router-redirect> elements.

import { TrailMap } from '@smore/trailmap';

/** More on this below */
const DocPaths = new Map<string, string>([
    ['hello-world', 'content/intro/hello-world.md']
])

...

<stencil-router>
    <stencil-route-switch scrollTopOffset={0}>
        <stencil-route url='/' component='page-home' exact={true} />
        <TrailMap base='/docs' component='page-docs' paths={DocPaths} />
        <stencil-route component='page-notfound' />
    </stencil-route-switch>
</stencil-router>

Rendering Content

The component you pass to component will be passed MatchResults with both name and path.

In order to render the content, you will likely need to do something like:

export class MyComponent {
    @Prop() match: MatchResults;

    componentDidLoad() {
        fetch(this.match.params.path)
            .then(res => res.text())
            .then(content => this.handleContent(content))
    }
}

If all of your content is an .md file contained in /content, then you might consider fetching using the paths value to store just the document path (intro/hello-world) and fetching content/${this.match.params.path}.md in the component

API

TrailMap Props

** base ** The base URL for this group of routes, for example /docs

** component ** The component that should be rendered when a route matches, for example page-docs.

** paths ** A Map<string, string> object containing all possible valid routes.

The key of each entry represents the url path, appended to base (for example, hello-world would become /docs/hello-world)

The value of each entry represents a path to the content, to be passed to the component as MatchResults.params.path (for example, /content/intro/hello-world.md)