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

electron-plugin-manager

v1.2.0

Published

Plugin Manager based on NPM for Electron apps

Downloads

15

Readme

electron-plugin-manager

Plugin Manager based on NPM for Electron apps

NOTE: Does not work with native node modules

Installation

$ npm i --save electron-plugin-manager

Usage

Let's assume our app name is Dotsync

Assuming we are storing the config data for our electron app in the %APPDATA%:

// In main process
const { app, ipcMain } = require('electron');
const epm = require('electron-plugin-manager');

const dir = path.join(app.getPath('appData'), 'Dotsync');

epm.manager(ipcMain);
// In renderer process
const { remote, ipcRenderer } = require('electron');
const epm = require('electron-plugin-manager');

const dir = path.join(remote.app.getPath('appData'), 'Dotsync');

Install

We can install a package from NPM as plugin by:

// In main process
epm.install(dir, 'is-number', 'latest', (err, pluginPath) => {
  // ...
});
// In renderer process
ipcRenderer.on('epm-installed-is-number', (event, err, pluginPath) => {
  // ...
});

ipcRenderer.send('epm-install', dir, 'is-number', 'latest');
// Response sent to `epm-installed-${name}` channel where `name` is the plugin name

Uninstall

We can uninstall an installed plugin by:

// In main process
epm.uninstall(dir, 'is-number', (err) => {
  // ...
});
// In renderer process
ipcRenderer.on('epm-uninstalled-is-number', (event, err) => {
  // ...
});

ipcRenderer.send('epm-uninstall', dir, 'is-number');
// Response sent to `epm-uninstalled-${name}` channel where `name` is the plugin name

List

We can list all the installed plugins by:

// In both process
epm.list(dir); // Array of name

We can list all the installed plugins along with their versions by:

// In both process
epm.list(dir, { version: true }); // Array of name@version

Load

We can load a plugin by:

// In main process
epm.load(dir, 'is-number'); // Loaded plugin
// In renderer process
epm.load(dir, 'is-number', remote.require); // Loaded plugin

Unload

We can unload a plugin by:

// In main process
epm.unload(dir, 'is-number');
// In renderer process
ipcRenderer.send('epm-unload', dir, 'is-number');

License

MIT/X11

Bug Reports

Report here. Guaranteed reply within a day.

Contact

Pavan Kumar Sunkara ([email protected])

Follow me on github, twitter