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

@abquintic/electron-plugins

v0.1.1

Published

Plugin loader for electron applications.

Downloads

4

Readme

electron-plugins

Plugin loader for electron applications.

Installation

npm install electron-plugins --save

Usage

In your electron render process you can load your plugins like so:

var plugins = require('electron-plugins');

document.addEventListener('DOMContentLoaded', function () {
  var context = { document: document };
  plugins.load(context, function (err, loaded) {
    if(err) return console.error(err);
    console.log('Plugins loaded successfully.');
  });
});

The context object may take the following additional, optional parameters:

  • pluginPath: String: The path to find plugins. Defaults to ApplicationRoot/plugins
  • Substitutes: ~ - User home dir per os.homedir() IF first character : - Application Name per package.json IF last character
  • Examples: ~/.config/: - /home/user/.config/MyApp ~: - /home/usr/MyApp
  • makePluginPath: Boolean: Create the plugin path if it is not found. Defaults to false
  • quiet: Boolean: Do not write to the console. Defaults to false.
  • plugins: An Object of user provided plugins in the format { pluginName: pluginVerionsString } using semvar compatible strings OR LINK for the version.

If you would prefer to do plugin discovery, you can load using the following:

var plugins = require('electron-plugins');

document.addEventListener('DOMContentLoaded', function () {
  plugins.discover( '', false, function ( err, results ) {
    var context = { document: document };
    if( !err )
    {
      context.plugins = results;
    }
    plugins.load({context: context}, function (err, loaded) {
      if(err) return console.error(err);
        console.log('Plugins loaded successfully.');
    });
  });
});

About your plugin:

The default plugin folder location is pulled from the AppDirectory object for the application if not provided by the app. Inside the plugins folder, your plugin should have directory matching its name. There should be a subdirectory for each version of the plugin installed, named for the version in semvar compatible format ( example: 0.0.1 ) or LINK for developmental code.

Your plugin will need a package.json. If config.main is not set, it is assumed to be index.js.

Your plugin should export a constructor function, which is passed the context object upon instantiation. You can put whatever you want onto the context object.

function Plugin(context) {
  alert("This plugin loaded!");
}

module.exports = Plugin

Examples

Related