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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@donkeyclip/motorcortex-waa

v1.0.4

Published

Your plugin description here

Readme

motorcortex-plugin-starter

Purpose

A starter plugin for creating MotorCortex plugins.

Structure and Contents

It includes:

  • rollup configuration & ready to use build tools
  • a pre-configured webpack for the needs of the demo
  • pre-configured eslint and babel
  • and a set of ready to work on, Incidents:
    • Effect, for developing a custom Effect
    • HTMLClip, for developing a pre-configured HTML Clip with HTML, CSS and Incidents
    • Combo, for developing custom, pre-configured Combos
    • Clip, for developing custom browser Clips, such as canvas

These Incidents are the starting point for developing a plugin. They extend the right Classes from MotorCortex SDK and they have blank implementations of all the methods that should or can be overwritten, with comments.

Along with the comments you can always refer to MotorCortex documentation for detailed information on how to implement a plugin.

How to use

Once you've decided what exactly your pluign is going to do and once we've decided on the type of Incident(s) you need to implement, you can start directly from the basic/blank implementations and either work on them directly or just copy them. Change the names of the files, name your Classes however you want but always make sure you import and expose everything properly on your index.js file.

Also, it's imortant to change your package.json file so you can name your pluign, provide details and more.

Commands

  • npm run build: builds the dist of your pluign along with the demo
  • npm run build:demo: builds just the demo
  • npm start: builds everything and starts the demo
  • npm start:demo: just starts the demo

Have fun!!!