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 🙏

© 2024 – Pkg Stats / Ryan Hefner

px5

v0.0.9

Published

Patcher for express

Downloads

3

Readme

About

Express patcher to add extra route info to request object - req. Can be used for group metrics for endpoints etc.

How it works

This patches application and Router's use, get, put, post, delete and patch methods to do the following things -

  • Whenever any handler passed to those functions is called, the path it was mounted on is added to a stack.
  • If the handler has a next method and it is invoked then path is popped from the stack.
  • If handler is an errorware then stack is not updated.
  • Freezes the stack once res.send is invoked and it is not updated any further.

Final state of the stack represents the route the request took.

Usage

import px5 from "px5";

//patch before importing express
px5.patch();

import express from "express";
...

once patch is applied successfully following operations can be performed -

  1. Get path taken by request so far
px5.getNormalizedPath(req); // example: /api/order/:type
  1. If you want to manually freeze the stack it can be done like this
px5.freezeStack(req);
  1. Check if stack is frozen or not
px5.isStackFrozen(req);

Want to contribute?

Make your changes, add a changeset using npx changeset and create a pr.

Todo

  • Add tests
  • Add methods to make it apply custom patches
  • Improve typing