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

riot-history-manager

v3.3.4

Published

```npm install riot-history-manager```

Downloads

61

Readme

riot wrapper for history-manager

Installation

npm install riot-history-manager

Usage

index.js

import "riot-history-manager";

// any code here

main.riot

<main>
    <router>
        <route path="" redirect="home" />
        <route path="home">
            <span>HOME</span>
        </route>
        <route path="page1">
            <span>PAGE 1</span>
            <img src="img.jpg" need-loading>
        </route>
    </router>

    <script>
        import { Router } from "history-manager";

        Router.setContext({
            // ...
        });
        Router.setContext({
            // ...
        });

        export default {
            onMounted() {
                Router.start()
            }
        }
    </script>
</main>

Routing cycle

As soon as the Router calls the route component listener, the latter mounts the slot in a child div element.

In this stage there is the mount cycle of riot.

Just after this the div element is set with display: none until the loading is complete, so you should consider this in any operation started in the mount cycle.

Now is dispatched the "beforeroute" event in every newly created element.

The route now is waiting all the need-loading elements to fire the "load" event.

When all they are done, it will dispatch the "unroute" event to the previous route - if any - and then unmounted it.

Now the div element containing the slot is set with display: block and is dispatched the event "route".

Following a more concise explanation:

  1. currentRoute.mount()
  2. display: none
  3. currentRoute.dispatchToChildren("beforeroute")
  4. waiting "load" from need-loading elements
  5. previousRoute.dispatchToChildren("unroute")
  6. previousRoute.unmount()
  7. display: block
  8. currentRoute.dispatchToChildren("route")