pluginbot | Plugin framework for creating extensible applications | Plugin library

pluginbot is a JavaScript library typically used in Plugin applications. pluginbot has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can install using 'npm i pluginbot' or download it from GitHub, npm.

At a high level - pluginbot is an app framework that consists of plugins which can provide/consume services. To define a plugin you define a function which provide services and a function that can consume services, consumption happens in the form of a redux-saga so your plugin can wait around for your desired service to be provided which elmiminates dependency chains entirely since your plugin will pause execution until the service it needs becomes available. This architecture allows for a highly extensible application because a plugin that adds functionality would just provide services other plugins consume (or consume services other plugins provide) - for example a plugin could provide new routes to be consumed by a router plugin or a plugin could provide UI components such as navigation-menus which would be rendered by a navigation-menu consumer. In order for plugins to run, they have to be declared in a configuration which will contain at a minimum the path of the plugin. Here you would define environment specific data. Configuration can either be json or a js file that exports an object/Promise that resolves to an object. The plugins array represents the enabled plugins in a pluginbot instance. A plugin consists of a module which exports a generator function, each plugin takes the form of a redux-saga meaning they can wait for specific events to happens or services to be provided by other plugins before running their own code. Now if I wanted to create a plugin which adds a new route to my app all I need to do is provide an expressRoute service. In order for a pluginbot plugin to be considered valid it requires a pluginbot section to be defined in the package.json. For a basic definition you just need to define where the entry point to your plugin is and the services the plugin consumes (if any).