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

@thejohnfreeman/joplin-plugin

v2.0.1-4

Published

Types and tools for Joplin plugins

Readme

@thejohnfreeman/joplin-plugin

Types and tools for writing Joplin plugins.

Versioning

This package is versioned after the version of Joplin from which it was extracted. In case multiple versions of this package must be published for a single version of Joplin, I attach a subversion to every release. In order for semantic versioning to choose the latest subversion, I specify it as a pre-release identifier, and I never publish a version without a pre-release identifier. For the pre-release identifier format, I chose to use a single number starting at 0 and incrementing with each release. I anticipate releasing only one version of this package for most versions of Joplin, and thus most versions of this package will look like 1.2.3-0.

How to start a new plugin

  • Add a dependency on @thejohnfreeman/joplin-plugin.
  • Add a build script that is joplin-plugin-build && joplin-plugin-pack.
  • Write your TypeScript source at src/index.ts.
  • Import the Joplin object with import joplin from '@thejohnfreeman/joplin-plugin'.
  • Import Joplin types with import { NamedType } from '@thejohnfreeman/joplin-plugin/types'.

How to convert an existing plugin

In the filesystem:

  • Remove GENERATOR_DOC.md, webpack.config.json, and the directory api.
  • Remove plugin.config.json if it is simply {extraScripts: []}, or if the only extraScripts are .js files.
  • You can likely remove tsconfig.json.

In package.json:

  • Remove dependencies on copy-webpack-plugin, fs-extra, glob, on-build-webpack, tar, ts-loader, webpack, webpack-cli, chalk, and yargs.
  • Add a dependency on @thejohnfreeman/joplin-plugin.
  • Remove scripts for dist, prepare, and update.
  • Add a build script that is joplin-plugin-build && joplin-plugin-pack.

In your TypeScript source code:

  • Replace all imports of the api module with imports of the @thejohnfreeman/joplin-plugin module.

Notes

This package includes NodeJS ES module "exports" that point to TypeScript sources just to quiet warnings from the plugin @rollup/plugin-node-resolve.

This package uses the typeVersions field to simulate submodule exports for TypeScript.