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

opam_of_packagejson

v0.1.2

Published

Simple tool to generate META, opam and .install files.

Readme

opam_of_packagejson

This is a simple executable that takes in a package.json and outputs an opam file. It can optionally generate the META file and .install file needed.

You can simply depend on it via npm. Add this to your package.json:

"opam_of_packagejson": "bsansouci/opam_of_packagejson"

To run you can just do add an npm script that runs opam_of_packagejson -gen-meta packagejson.

It'll need some help figure out the opam dependencies. Add this to your package.json if you need to depend on opam packages:

  "opam": {
    "dependencies": {
      "opamLibThatYouDependOn": "build >=  \"1.13.3\""
    },
  },

The constraints for the version numbers are opam constraints that you can read about here.

If you want to also generate the META and .install file, add this

  "opam": {
    "installPath": "_build/src"
  },

Though the default is "_build/src"

This is roughly the same as what you'd expect to see inside a pkg/pkg.ml when using topkg to generate the .install file.

You can add -gen-install and -gen-meta to the command to generate those.

You can add libraryName under opam to control the name of the opam version of your library. If not specified, the default is to use the package.json's name.

You can also add mainModule under opam to control the name of the main outputted library file when the library is built. If not specified, the default is to use the package.json's name.