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

@longucodes/plugin-system-loader

v0.1.7

Published

### Purpose

Downloads

3

Readme

@longucodes/plugin-system-loader

Purpose

This package provides a Nestjs module for dynamically loading modules during runtime. The goal is to create a way of extending ready-to-go services without needing to edit their code.

Developer usage

To use the system, import the module in your application

import {Module} from "@nestjs/common";
import {PluginModule} from "@longucodes/plugin-system-loader";

@Module({
  imports: [
    PluginModule.forRoot({})
  ]
})
export class AppModule {}

Optionally, path to the definition file can be provided

import {Module} from "@nestjs/common";
import {PluginModule} from "@longucodes/plugin-system-loader";

@Module({
  imports: [
    PluginModule.forRoot({pluginsDefinitionFilePath: '/path/to/plugins.json'})
  ]
})
export class AppModule {}

It's recommended to use this module in conjunction with @longucodes/plugin-system-cli for runtime installation of plugins.

End-user usage

To add a plugin, add plugins.json file in the directory, where microservice is running and add plugin definitions. The file should consist of an array, with each entry representing one plugin.

Simple definition

Simples plugin definition is just the name of the NPM package

[
  "plugin-name"
]

The plugin will be automatically installed by the cli and loaded into the application.

Advanced definition

To add more capabilities, like config or specific version, advanced definition should be used.

[
  {
    "name": "plugin-name"
  }
]

In addition to name, following properties can be provided.

  • version - install specific version of the package
  • mode - can be static (default) and dynamic. Dynamic plugins will not be installed by cli
  • config - object with configuration values
Config

The config object can contain direct values or read them from environment. To use environment variable , the config value should be the name of the environment variable with $ at the beginning. All variables consisting only of uppercase letters and _, and a $ will be treated as a environment variable read.

[
  {
    "name": "plugin-name",
    "config": {
      "staticVariable": "123",
      "dynamicVariable": "$SOME_VAR"
    }
  }
]

Not all plugins are configurable, check documentation of used plugin.

Plugin development

To create your own plugin, create NPM package, that default exports a Nestjs module. If you want your package to be configurable, add static method forRoot returning a dynamic module.