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

@jsbooks/local-api

v1.0.2

Published

Will be run on the users machine when they use jbook application. User will not being running the development server because it takes up a lot of resources and is slow to start up.

Readme

Local-API

Will be run on the users machine when they use jbook application. User will not being running the development server because it takes up a lot of resources and is slow to start up.

get / Sends back index.html or index.js for React App. Will get loaded in users browser.

get /cells Find the list of cells stored in a file (name provided in the CLI) and sends those back to the browser.

post /cells Take the list of cells from the browser and stores them into a file.


Using express to handle the requests.


How to run locally

cd cli
cd dist
node index.js serve

//in jbook
npm start

cli/dlist: node index.js server Runs on port 4005 root packages: npm run start Runs on port 3000 Create new build: local-client: npm run build

Adding packages:

lerna add --scope=<file name> <package name>  

Lera - link packages

lerna add local-client --scope=local-api

Which packages to serve?

When we are actively developing our app on our local machine, we want to use the local-api package with create-react-app dev server.

When we are running our app on a user machine, we want to serve up the build files from build directory.

Inside of CLI, we need to decide if we are running on our local machine for development or on a user machine for production. Before we ship to NPM, we must run a script to search for 'NODE_ENV" and set it to 'production'.

const isProduction = process.env.NODE_ENV === 'production'; // keep for local machine
const isProduction = 'production' === 'production'; // keep for production when shipping to NPM