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

mx-host-core-worker

v0.3.0-a

Published

Generic worker code for a Matrix application host

Downloads

7

Readme

mx-host-core-worker

Generic worker code for a Matrix application host

This is designed to run in a shared or service worker in my work-in-progress Matrix app host. This is the only part of that app host that would maintain any state; The other part would be stateless except for the URL and query parameters and will be using Vue.JS.

This is using my rpcchannel library that creates a standard interface for the app host and app tabs to connect to. This is versioned using semantic versioning, so this will be released independently of the app host code. When a change is made, the API is tested using the .api.js tests (which only call the RPC functions) and unit tests (coming soon). This allows for a much nicer workflow where features are first implemented and then the corresponding UI is implemented.