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

swyft-plugins

v1.0.8

Published

Plugin system for JavaScript projects

Downloads

23

Readme

Have you ever wanted to create a plugin system for your JS app? Well, now you can, easily.

Info

If you call onStart or onExit, it will execute those functions of all of the plugins at the same time. onInvoke is plugin specific and will only execute for the plugin you mention.

They all accept array of arguments, so you can pass data to the plugin. You can also return data from the plugin using invoke to the app (using generics).

You can call onStart, onExit and onInvoke whenever you want. init calls upon itself on the start of the app.

Install

npm i swyft-plugins

Usage

Create plugins.ts file:

import { PluginManager } from 'swyft-plugins';

const pluginManager = new PluginManager();

// DO NOT MODIFY ANYTHING ABOVE THIS LINE
// ADD YOUR PLUGINS BELOW THIS LINE
pluginManager.registerPlugin(require('./plugins/samplePlugin'));

// DO NOT MODIFY ANYTHING BELOW THIS LINE
pluginManager.initializePlugins();

export default pluginManager;

Create plugins/samplePlugin.ts:

import { Plugin } from "swyft-plugins";

const samplePlugin: Plugin = {
  name: "samplePlugin",
  init() {
    console.log("SamplePlugin: Initialized.");
  },
  onStart() {
    console.log("SamplePlugin: App has started.");
  },
  onExit() {
    console.log("SamplePlugin: App is exiting.");
  },
  async onInvoke<T>(...e: any[]): Promise<T> {
    console.log("SamplePlugin: Invoked.");
    return Promise.resolve("hi" as unknown as T)
  },
};

export = { ...samplePlugin };

Call it in your app:

import pluginManager from './plugins';
// DO NOT MODIFY ANYTHING ABOVE THIS LINE

console.log('This is the main application.');

const callMe = async () => {
  const test = await pluginManager.invoke("samplePlugin");
  console.log(test)
};

callMe();

Changelog

Made invoke asynchronous, as well as created an optional generic type for it, so you can explicitly define your return types.