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

new-core

v0.0.0

Published

create a new node distribution as easy as duct-taping things to it

Readme

new-core

give node a new core.

This module makes it easy to create an alternative distribution of node with different core modules. Via a few carefully placed hacks in node's module system, you can now make a node executable which now comes shipped with extra modules which are always available, as fs or net or http currently are.

Let be clear, I wish I didn't need to do this, but npm is just not reliable or secure enough (especially for binary addons) to distribute the kind of software I am making (cryptographically-secure decentralized databases) but this approach allows me to create a stable core that includes the C-touching bits (and it rarely changes, that is the point of core) and then have a rapidly changing javascript layer.

example

#! /usr/bin/env node

//shim some binary modules, which are useful for p2p
require('new-core')({
  level: require('level'),
  chloride: require('chloride'),
  utp: require('utp-native'),
  webrtc: require('webrtc'),
})

//and use the following boiler-plate to run a file

//mutate the argv, so that it looks like the current script is a real executable.
process.argv.splice(0, 3, 'new_core', require('path').resolve(process.argv[2]))

//and execPath...
process.execPath = __filename

//then call run main, to execute the file
require('module').runMain()

now you can publish that on npm (useful for dev) to make a bundle that is an executable, my plan is to use electron, since there are already tools to bundle that, and we are using electron for the UI anyway.

other ideas

you could also use this to turn off node core, and make a coreless node from node. see also nucelus and nojs

License

MIT