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 🙏

© 2026 – Pkg Stats / Ryan Hefner

imdone-api

v2.0.1

Published

Plugin API for imdone

Downloads

99

Readme

imdone-api

A plugin api for imdone: Kanban for Developers: In Your Markdown and Code.

Creating a plugin for Imdone

  1. Create a plugins folder under your project's .imdone folder. /my/project/path/.imdone/plugins
  2. Create a folder for your plugin under plugins and give it a name like MyPlugin. My directory structure looks like this...
    .imdone
    ├── config.yml
    └── plugins
        └── myPlugin
            ├── index.js
            ├── node_modules
            ├── package-lock.json
            └── package.json
  3. Look at imdone/imdone-sample-plugin: A sample plugin for Imdone for inspiration.
  4. Review the plugin api docs
  5. To make your plugin available for all imdone users, open a PR at imdone/imdone-plugins.

Naming your plugin

To identify your plugin imdone requires an implementation of the Plugin class get pluginName method. This method should return a string that is the name of your plugin. The name should follow these guidelines:

  • Use camelCase for the name of your plugin. For example, myPlugin.
  • Don't use the name imdone in your plugin name. This is reserved for the imdone core.
  • Use a name that describes what your plugin does.
  • Use a name that is unique to your plugin. This will help avoid conflicts with other plugins.

Join the discussion on discord