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

@spec-this/cli

v1.5.0

Published

CLI tool for Spec-This code intelligence platform

Downloads

147

Readme

@spec-this/cli

//force update

Official CLI tool for the Spec-This code intelligence platform.

Debug Mode

The CLI includes comprehensive debug logging to help troubleshoot issues, especially with API calls.

Enabling Debug Mode

You can enable debug logging in several ways:

1. Using the --debug flag:

spec-this scan --debug

2. Using the --log-level flag:

spec-this scan --log-level debug

3. Using environment variables:

export SPEC_THIS_DEBUG=true
spec-this scan

Or:

export SPEC_THIS_LOG_LEVEL=debug
spec-this scan

4. For a single command:

SPEC_THIS_DEBUG=true spec-this scan

Log Levels

Available log levels (from most to least verbose):

  • trace - Very detailed trace information
  • debug - Detailed debug information (includes all API calls and responses)
  • info - General informational messages (default)
  • warn - Warning messages
  • error - Error messages
  • fatal - Application crashes

What Debug Mode Shows

When debug mode is enabled, you'll see:

  • Every API request with method, endpoint, URL, and authentication status
  • Request body size and preview (for POST/PUT requests)
  • Response status, timing, and preview
  • Detailed error information including 413 errors with payload size
  • Batch splitting information (when scan data is split into batches)
  • Scan statistics (file counts, symbol counts, etc.)

Troubleshooting 413 Errors

If you're getting 413 (Payload Too Large) errors, debug mode will show:

  • The exact size of the request that failed
  • Whether batching is being used
  • How many batches are being sent and their sizes

This information can help determine if the batch size needs to be reduced or if there's an issue with the API server configuration.