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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@reason-native-web/h1-lwt

v1.2.2001

Published

This repo is used for publishing packages to npm that are either unreleased or depend on unreleased packages. This removes the need for resolutions in users' package.json.

Downloads

11

Readme

Vendor

This repo is used for publishing packages to npm that are either unreleased or depend on unreleased packages. This removes the need for resolutions in users' package.json.

Add a package

This example uses websocketaf

Add the git submodule, it is important that you use the https version because of the github workflow:

git submodule add https://github.com/anmonteiro/websocketaf.git

Create a websocketaf.json and whatever else is needed, in websocketaf's case we also need websocketaf-lwt.json and websocketaf-lwt-unix.json.

Note: I usually just copy another package that is similar, in this case h1.json

Check the coresponding .opam file, eg. websocketaf.opam, websocketaf-lwt.opam and websocketaf-lwt-unix.opamfor dependencies and add them to the json files accordingly.

Add build instructions under esy:

"esy": {
    "build": "dune build --only-packages=websocketaf --profile=release -j 4 --root=./websocketaf",
    "install": "esy-installer #{self.target_dir / 'default' / 'websocketaf.install'}"
}

Add a files key that points to the folder where it's cloned, in this case : "files": ["websocketaf"],

Update publish.yml with the added libraries in the topological order. The order is important if a library depends on another library since they will be published in order to be able to build the next.