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

@glensorbo/requestlogger

v1.1.0

Published

Simple http logger middleware for expressjs

Downloads

284

Readme

Request logger

Output will be something like this image

requestLogger uses dayjs for timestamp. It will show local time as configured at host the code is running on. If it's in development on your local computer, it should show the same timestamp as your computer. If running in docker, it will show timestamp as the docker container is configured. Defaults to UTC. To alter this in docker, start your container with environment: TZ= Example: TZ=Europe/Oslo.

Install by running

npm install @glensorbo/requestlogger
yarn add @glensorbo/requestlogger

Use by setting middleware at app level, or per route. App level will run this middleware for every request on every route.

import { requestLogger } from '@glensorbo/requestlogger';
import express from 'express';
import type { Express } from 'express';

const app: Express = express();
// requestLogger used as middleware on app level
// will be used on any route after this line
app.use(requestLogger);

app.get('/', function (req, res) {
  res.send('Hello World');
})

app.listen(3000);
import { requestLogger } from '@glensorbo/requestlogger';
import express from 'express';
import type { Express } from 'express';

const app: Express = express();

// requestLogger as middleware which can be used at any route
app.get('/', requestLogger, function (req, res) {
  res.send('Hello World');
})

app.listen(3000);

You can define it at app level to run on all routes, but define a route before middleware. Then logging will not happen on that route. In my case I don't want to log out all requests to the '/health' endpoint

import { requestLogger } from '@glensorbo/requestlogger';
import express from 'express';
import type { Express } from 'express';

const app: Express = express();

// requestLogger will not trigger on this route as it's being used after this endpoint
app.get('/health', function (req, res) {
  res.send('OK');
})

// requestLogger used as middleware on app level
// will be used on any route after this line
app.use(requestLogger);

app.get('/', function (req, res) {
  res.send('Hello World');
})

app.listen(3000);