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 🙏

© 2025 – Pkg Stats / Ryan Hefner

mcplugin

v1.0.2

Published

This Repository contains the Source of the McPlugin tool.\ This Tool is an all-in-one build-system/debugger for Spigot Plugins!

Readme

This Repository contains the Source of the McPlugin tool.
This Tool is an all-in-one build-system/debugger for Spigot Plugins!

how does it work?

easy. we've had tools like vscode, maven and the redhat java extension for vscode for years now. but it doesn't integrate nicely with spigot plugins - this is where "mcplugin" comes in!

with it you can easily manage your plugin settings, minecraft version, debugging and more. it nicely and quietly generates the correct configs for vscode, downloads and manages your maven dependencies, manages your different spigot versions in a central cache and last but not least: it does support debugging your plugin at runtime and hotreload on code change aswell!

Usage

before usage you need to install it globally with npm e.g. npm i -G mcplugin

to create a project type mcplugin init <version> <plugin-name> <your-group-id>
to rehydrate a cloned repo or to clean your repo type mcplugin hydrate
to test without debugger type mcplugin test
to build the plugin type mcplugin build

the plug.conf.js

in this file your plugin parameters are set. for example maven dependencies or your minecraft version.
after changes to this file you need to rehydrate your project in order to download all necessary dependencies.

the .plug folder

the .plug folder in your project contains your development server aswell as compiled java files (.class files) for makefile like behavior which only recompiles changed sources.
it also contains your most recent "plugin.jar" a.k.a. your plugin

the .plug_cache folder in your home folder

this folder contains all the different api jars, maven dependency jars, and spigot server jars to avoid having multiple copies of everything

currently under construction

  • automatic jdk detection (only works on windows currently. hold tight my fellow linux and mac users!)
  • maven dependency system currently broken
  • weird edge cases of minecraft version incompatabilities

Thanks!

a big thank you goes out to the dev team of papermc, spigot and craftbukkit for providing such an awesome platform for creating minecraft plugins