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

node_typescript_tutorial

v1.0.0

Published

This boilerplate is intended to be used to create new projects for node.

Readme

Node TypeScript Boilerplate

Description:

This boilerplate is intended to be used to create new projects for node.

Rationale

The boiler plate includes route handling, error handling, rate limiter with redis and also logging.

Project Structure

This boilerplate shows how routes are handled with a router and also handlers. It is advisable to use the asyncHandler from express-async-handler. I show this at errorTest.ts in the router. Try using route GET /six with and without the asyncHandler. Without it the program will stop cause the unhandled rejection. With asyncHandler at least it will throw an error but the app will not stall.

Needless to mention that the above should never happen if all the exceptions are caught appropriately in the program as shown for routes one to five and seven.

The app also uses an instance of Winston to log the messages. Feel free to modify it according to your needs, for example, you might send all the errors to a queue instead of a file. Or to send it to an APM manager. It is up to you. I think that the wrapper used there should be implemented to make sure all the messages share the same format though.

There is also a rate limiter in place. To use it make sure you have a redis server up and running. Please create a .env file following the .example.env. There is also a .env checker in utils to make sure all the .env vars are available and also exports them to be used anywhere.

Not sure if I am missing anything, I will keep updating this

To be done

Next I am planning to add docker to this boiler plate. Perhaps some connnections to different DBs as well . And of course some testing with Jest.

Help

If you have any suggestions please feel free to contact me at [email protected] or by a MR.

Run it

Clone it, npm install and then npm run start:dev