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

tail-gazer

v1.0.1

Published

Tail Gazer is a command-line tool for tailing logs of multiple services.

Downloads

125

Readme

Tail Gazer

Tail Gazer is a command-line tool for tailing logs of multiple services.

Installation

Install the package globally with npm:

npm install -g tail-gazer

Usage

The tool expects a configuration file in JSON format, with an array of service objects. Each service object should have the following properties:

  • name: The name of the service.
  • dir: The working directory for the service.
  • command: The command to start the service.
  • logFile: (optional) The file path to log service output to.

Example configuration:

{
  "services": [
    {
      "name": "Frontend Service",
      "dir": "./frontend",
      "command": "npm run dev",
      "logFile": "./logs/frontend.log"
    },
    {
      "name": "Backend Service",
      "dir": "./backend",
      "command": "python app.py",
    }
  ]
}

To run Tail Gazer, navigate to the directory containing your configuration file and run:

tail-gazer

By default, Tail Gazer looks for a file named tail-gazer.json. You can specify a different file with the --config or -c option:

tail-gazer --config my-tail-gazer-config.json

The tool will tail the logs of all services specified in the configuration file, printing the output to the console. The tool also creates a tail-gazer-logs directory in the current directory and saves log files there, if logFile property is provided in the configuration.

License

This project is licensed under the MIT License.