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

pack-mmip

v2.0.0-rc2

Published

Automatic packer for MediaMonkey Extension (MMIP) files. Run npm install, and Add this folder to your system PATH, then you can run pack-mmip and pack-zip.

Downloads

57

Readme

pack-mmip

Automatic packer for MediaMonkey Extension (MMIP) files. Requires Node.js and NPM.

Installation

  1. Run npm install --global pack-mmip.
  2. Then, you can run pack-mmip and pack-zip.
  3. If the commands do not work, make sure your NPM folder is added to your system PATH. (On Windows, it should be under %appdata%/npm.)

Usage

pack-mmip (path to directory) (path to packed extension OR just its name) (options)

OPTIONS:
        -a      --AppendVersion         Read the project's version from its info.json and append it to the
                                        filename. For example: MyAddon-1.2.3.mmip
        -b      --PutFileIntoBin        Put resulting file into a subfolder named "bin"
        -d      --Debug                 Debug logs. Please use this if you encounter a bug, and paste the
                                        logs into a new GitHub issue.
        -h      --help                  Print this help text and exit
        -i      --IgnoreDefaults        Ignore configuration rules
        -o      --OpenAfterComplete     Open file (Install to MediaMonkey) after complete
        -s      --ShowAfterComplete     Show in folder after complete
        -v      --version               Print version and exit
        -y      --Yes                   Automatically answer "yes" to prompts

        -p      --PreambleFile <name>   File containing a preamble to be added to the top of text files.

TO IGNORE CERTAIN FILES:
                                        Add a file named .mmipignore or .archiveignore in your project root.
                                        It uses glob syntax similar to .gitignore
                                        (see https://www.npmjs.com/package/glob)
TO CONFIGURE DEFAULT BEHAVIOR:
        pack-mmip config                Different configuration files are saved for pack-mmip and pack-zip.

If path to packed extension is not specified, it will default to the name of the folder.
Additionally comes with a command pack-zip if you wish to use it to output a ZIP file instead of MMIP.

ADDITIONAL UTILITIES:
        --dev <path>                    Tool that temporarily "mounts" your addon to MediaMonkey's scripts/
         [--data-folder <path>]         skins folder, making development easier. Just restart MediaMonkey
                                        for your changes to take effect, instead of having to re-pack and
                                        re-install your addon. Watches & compiles any TS files as they change.

        --init                          Tool that automatically creates a new info.json file in the current
                                        folder, after prompting for title, ID, version, etc. Similar to `npm init`.
                                        Also, optionally initializes TypeScript support for code hints.
TYPESCRIPT INFORMATION:
        pack-mmip enables you to write addons in TypeScript by integrating with the mediamonkey NPM package,
        which contains type declarations for MediaMonkey's source code. During the build step, pack-mmip
        transforms imports into the format that MediaMonkey expects, with correct relative paths, e.g.
        import Multiview from "mediamonkey/controls/multiview" -> import Multiview from "./controls/multiview"

Examples:

# Packs C:/projects/MyPackage into C:/projects/MyPackage.mmip
pack-mmip C:/projects/MyPackage

# Does the same as above, but with relative paths instead of absolute paths
cd C:/projects/MyPackage
pack-mmip .
# If you do not provide a file name, the output file name will be based on the folder name. You can provide the output file name as a second argument.
pack-mmip . MyPackageName
pack-mmip . MyPackageName.mmip

# The -s argument will open a file explorer window containing the newly packed file.
pack-mmip ./ ../MyPackage -s

# The -o argument will attempt to run the file, causing MediaMonkey to install it.
pack-mmip ./ ../MyPackage -o

TypeScript information

pack-mmip enables you to write addons in TypeScript by integrating with the mediamonkey NPM package, which contains type declarations for MediaMonkey's source code. During the build step, pack-mmip transforms imports into the format that MediaMonkey expects, with correct relative paths, e.g. import Multiview from "mediamonkey/controls/multiview" -> import Multiview from "./controls/multiview"

Running pack-mmip --init will prompt you to set up TypeScript support. Doing so is highly recommended. You do not need to write your addon's code in TypeScript. The default tsconfig.json that is created will enable type hinting for JS files as well.

If type hinting does not show up, or you see an error saying that the package "mediamonkey" could not be found, you may have to run npm install --save-dev mediamonkey in your project.