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

pino-ui

v0.0.1-alpha.13

Published

This library is an improvement of pino-pretty. Sometimes it's too complicated to browse through console logs and understand all logs on a specific request.

Downloads

435

Readme

pino-ui

This library is an improvement of pino-pretty. Sometimes it's too complicated to browse through console logs and understand all logs on a specific request.

This library adds a web view for the pino logs.

Installation

npm install pino-ui --save-dev

Usage

The usage is similar to pino-pretty which is quite simple, all you need to do is pipe to pino-ui.

node server.js | pino-ui

Configuration

You can configure:

  • The columns you want to display on the table
  • The columns you want to display on the details and how to display them
  • Which column has a request identifier or trace id
  • The port it's going to use to serve the UI

We're using JSON to read the configuration.

Important: You need to add the json file with the following name (.pino-ui.json) on the cwd of your application

| Field | Type | Description | | ------------------- | ------- | ------------------------------------------------------------ | | gridColumns | Column | How to display the grid columns | | detailColumns | Column | How to display the log data on the details | | traceColumn | String | The column used for trace so we can easily separate all logs in a single trace | | port | Number | The port to serve the UI (Default 8080) | | autoReset | Boolean | If auto reset when process is restarted, default to false | | ascending | Boolean | Wether sorting will be ascending or not, default to false (descending) | | chartWindowMinute | Number | Window to capture number of logs in the log chart. Default to 1 (minute) |

Column Type

| Field | Type | Description | | ----------- | ------ | ------------------------------------------------------------------------------------------- | | name | String | Label of the column | | key | String | The key we're going to use to render the column | | formatter | String | text, multiline_text, numeric, code, sql, json, uuid, duration, timestamp |

JSON Example

{
  "gridColumns": [
    { "name": "Req #", "key": "reqId" },
    { "name": "User", "key": "context.userId" },
    { "name": "Message", "key": "msg" },
    { "name": "GraphQL Field", "key": "graphqlFieldName" }
  ],
  "detailColumns": [
    { "name": "Req #", "key": "reqId" },
    { "name": "User", "key": "context.userId", "formatter": "code" },
    { "name": "Message", "key": "msg" },
    { "name": "GraphQL Field", "key": "graphqlFieldName", "formatter": "code" },
    { "name": "SQL", "key": "sql", "formatter": "code" },
    { "name": "Parameters", "key": "parameters", "formatter": "json" }
  ],
  "traceColumn": "reqId"
}