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

bff_public_web

v1.0.0

Published

bff_public_web

Readme

Bff public web

Local execution

  • Initialize as typescript project
func init --worker-runtime typescript
  • Install dependencies

Before installing the dependencies, configure your .npmrc file following the example you will find in keeper. Without this step you will not be able to install some of the necessary dependencies as shared repositories in Azure.

npm install
  • A build must be created for each change in code
npm run build
  • Launch function
npm start // func start

Now the console should show the exposed endpoints

Environment Variables

You can see a list of the environment variables in the .env.dist file Environment variables are added to local.settings.json

Some tests may need environment variables, these should be in a traditional .env file

Example:

{
    "IsEncrypted": false,
    "Values": {
      "AzureWebJobsStorage": "UseDevelopmentStorage=true",
      "FUNCTIONS_WORKER_RUNTIME": "node",
      "MY_ENV_VARIABLE": "VALUE"
    }
}

Testing

The current tests are end to end, one of the problems is the cold starts of the functions on which it depends, momentarily we must warm up these functions before launching the tests so as not to exceed the jest waiting time

Once the functions are "warmed up", execute the following command:

npm run test