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

@sigma-db/napi

v0.4.2

Published

A utility to setup an environment for development of native Node.js modules.

Readme

N-API CLI

NPM node version

This project eases the process of setting up an environment for developing native Node.js modules by fetching the correct architecture- and OS-specific header and library files as well as preparing the CMakeLists.txt acxcordingly.

Prerequisites

Currently, this tool requires cmake and ninja to be in your PATH, as well as a working C/C++ toolchain.

  • On Windows, you can use the Visual Studio Build Tools which includes all required tools. In that case, make sure that you use the appropriate Tools Command Prompt for Visual Studio
  • On Linux and other UNIX-like environments, make sure to have cmake, ninja, clang/gcc and ld available in your PATH.

Installation

Run npm i -g @sigma-db/napi to install the napi CLI globally.

Usage

Assume we want to create and build a project named native.

  1. create the project and change into its directory by running napi new native && cd native.

  2. initialise the project by running napi init from within the project directory to automatically download the appropriate header and static library files.

  3. build the project by running napi build from within the project directory.

  4. test that requiring your native module actually works by running napi test from within the project directory. You should see an output like A project named "native" is growing here.

  5. clean any files generated during the build by running napi clean from within the project directory. Note that doing this will make CMake run again on the next build, considerably increasing the build time of the next build.

Changing the Node.js version

If you happen to change to version of Node.js, you will also require new header and static library files. In that case, run napi clean all, which will delete any previously downloaded header and library files, as well as any built files.

Disclaimer

The current code was written in a single 16h session and might need quite some refactoring and more user-friendly error-handling — I'd love to see people contributing.