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

jsreport-nexe

v1.3.1

Published

create single executables out of your [node/io].js applications

Readme

#jsreport-nexe

Some minor adaptations to make nexe working with jsreport

  1. Transform bundle and add require.resolve to all modules where it is used
  2. Alter bootstrap_node.js and replace throwing errors with doing native require
  3. Excluded nexeres from browserify to avoid resources duplication
  4. Bundle option which just bundles the js and skip node.js download and compilation to enable quick testing
  5. Embedding resources works in differn't way to optimize startup time and compilation of big resoruces. Instead of base64 encoding strings into js, it writes binary data inside the exe file into the end. These binary data are then read and parsed when nexeres is required
  6. Avoid replacing invalid asci characters from the bundle