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

ftail

v1.0.0

Published

Pretty print tailed logs. Fully configurable APIs. Works with common logging libraries like winston, bunyan

Downloads

10

Readme

Pretty print logs while keeping them streamable!

Overview

This project provides a CLI tool for beautifying the output of log files. The tool is configurable via a .ftailrc file in the user's home directory. It uses the chalk library to style and format log outputs, making it easier to read and analyze.

Installation

To install the CLI tool, you need to have Node.js and npm installed. Then, you can install the tool using the following command:

npm install -g ftail

Configuration

To set up the configuration file, create a .ftailrc file in your home directory with the following content

{
  "mapper": {
      "header": "time",
      "headerType": "date",
      "highlight": ["msg"],
      "flatten": ["err", "token"],
      "divider": "\n\n",
      "formatters": {
        "err": {
          "highlight": ["message", "name"],
          "header": "name",
          "headerTitle": "Error"
        },
        "token": {
          "headerTitle": "token"
        }
      }

  },
  "theme": {
    "mode": "dark"
  }
}

Mapper

  • header: The field used as the header of each log entry.
  • headerType: The type of the header (e.g., date).
  • highlight: Fields to be highlighted in the log entry.
  • flatten: Fields to be flattened in the log entry. For example, nested objects.
  • divider: The divider string used between log entries. For example, new line.
  • formatters: Custom formatters for nested fields following the same structure as config. For example if you want to highlight err.message. Check usage in example.

Theme

mode: The theme mode (dark, light, or custom). If you choose the custom theme mode, you need to provide a custom theme object with the following properties:

{
  "color": "black",
  "headerColor": "magenta",
  "highlightBg": "bgYellowBright",
  "highlightColor": "black"
}

Note: Only chalk foreground and background colors are supported for now.

Usage

After configuring the .ftailrc file, you can use the CLI tool to format your log files. Run the tool with the following command:

ftail "$(ls -t | grep 'error' | head -1)" // the recent error file in logs directory

License

This project is licensed under the ISC License. See the LICENSE file for more details.

Contributing

Contributions are welcome! Please open an issue or submit a pull request with your changes.