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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@mctools/errors

v1.2.3

Published

Scan debug.log file to find unknown errors

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

krutoy242krutoy242

Keywords

automationminecrafttoolscicli

Readme

Scan debug.log file to find unknown errors

Terminal usage example

In large modpacks, the debug.log file can contain hundreds of thousands of lines. This tool filters out unimportant and cluttered messages, leaving only the most critical ones.

Features:

  • Log Trimming: Can cut the log file to a specific point (e.g., before the player joins the world).
  • Message Sanitizing: Replaces parts of messages for better readability (removes timestamps, hash codes, UUIDs).
  • Stack Trace Shortening: Truncates long stack traces.
  • Error Grouping: Groups identical errors together.
  • Advanced Filtering: Ignores a huge number of known harmless errors and warnings from many mods.

Usage

  1. Install latest NodeJS for Windows or Unix

  2. Open console, navigate to your Minecraft directory (one with the mods/ directory or options.txt file)

    > cd C:/Instances/MyModpack

  3. Run:

    > npx @mctools/errors --help

Options

Scan debug.log file to find unknown errors (@mctools/errors)

USAGE @mctools/errors [OPTIONS] 

OPTIONS

                                                        -o, --output    Path for output with errors. If not specified output into stdout.
                                          -l, --log="logs/debug.log"    debug.log file path (may need to be enabled by launcher)         
  -c, --config="packages\errors\src\config.yml"    Path to .yml file with configs

Author

  • https://github.com/Krutoy242

Other tools