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

@warp-works/warpjs-plugins

v2.0.1

Published

WarpJS plugins utilities

Downloads

6

Readme

WarpJS Plugins

Library to manipulate WarpJS plugins. See the HOWTO to learn how to write your own plugins.

API

.init(domainName, persistenceConfig, pluginsConfigs)

Initializes the plugins. The domainName is the string representing the default domain to work with. The persistenceConfig is an object like:

{
  module: "npm-package-implementation-of-persistence",
  host: "your-persistence-host",
  name: "your-default-persistence-storage"
}

The pluginsConfigs is an array of:

{
  name: "string",
  type: "optional to describe a feature",
  moduleName: "@some/module to use in a require()",
  path: "/path where to mount the plugin",
  config: {
    something: "that the plugin will need and understand"
  }
}

If a type is defined, all plugins with a given type should implement the same API (this API is out of scope for this module).

See RESERVED_PLUGIN_TYPES for a list of reserved plugin types. You can defined your own types, but these will affect Studio and Content sides.

.getPlugins([type])

Gets all the plugins with the plugin.type===type. If type is not defined, all plugins are returned.

.getPlugin(type)

Returns the last plugin with the type === type.

.getPluginByName(name)

Returns the last plugin with the name === name.

.info()

Returns a basic info object for each plugin. The format is:

{
  name: "Name of the plugin",
  moduleName: "npm-module-name",
  type: "optional to describe a feature",
  path: "/path where to mount the plugin",
  version: "plugin's package.json's version"
}

.register(warpCore, app, baseUrl, staticUrl)