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 🙏

© 2025 – Pkg Stats / Ryan Hefner

dialogflow-fullfiller

v1.0.0

Published

![NodePing status](https://img.shields.io/nodeping/status/05jubzo0-6vz7-4s2n-82tb-cf8b4sxoe70g?label=Dialogflow%20Production)

Readme

Documentation

Environment

Install the app on your computer

You must have installed on your computer :

  1. run npm run setup from your terminal to install all required packages.
  2. Get an .env file from an admin of this app.
  3. Make sure to have the Github CLI installed as we use gh run watch in the deployment script

Start the app

npm run start:watch to start the app locally and enjoy the hot reload thanks to Nodemon.

npm start to test the production build

lsof -ti tcp:3000 | xargs kill if you need to kill other running apps on port 3000

Config files

package.json - Node main app config - npm depencies, local scripts, etc.

app.json - Heroku (our server) config file.

Nodemon.json - Nodemon is purely used locally to automatically restart the app when a file is modified.

jest.config.json - Jest is a unit test package.

ts.config.json - Typescript configuration file.

.prettierrc - Prettier configuration file for file formatting.

.github/workflows node.js.yml - Where Github workflows are written.

CRON JOBS

CRON jobs are triggered by a Heroku add-on here.

node fileLocation.js

Environment variables

Config variables are set in a local .env at the root folder.

From this .env var:

If you modify, please update the .env.example file. using npm run regenerate-env-example.

ENVIRONMENT has three value: development, staging and production DEBUG_MODE has two string values: ON or OFF - It will dislay log entries with debug as severity. See the custom logger

heroku config --app APP_NAME_HERE To display env vars on heroku through the CLI

Useful command lines

prettier --write .

Useful links

  • Visual representation of our tech stack on Kumu.