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

remark-config-inspector

v2.2.3

Published

A visual tool for inspecting and understanding your remark and remark-lint configs

Readme

Remark Config Inspector

npm license. npm total downloads. latest GitHub release. GitHub stars. GitHub forks. GitHub open issues. codecov.

A visual tool for inspecting and understanding your remark / remark-lint configuration.

It helps you understand:

  • which config items are active,
  • where rule states come from,
  • how overrides and file globs affect resolution,
  • and how final rule behavior is composed.

Screenshot

Usage

From a project that contains a remark config (.remarkrc* or package.json#remarkConfig):

npx remark-config-inspector@latest

Then open http://localhost:9999/ (If it does not open automatically) to explore your config.

Resolve for a target file

Use a specific target file when you want context-sensitive resolution:

npx remark-config-inspector --target docs/guide.md

If neither --file nor --target is supplied, the inspector uses a synthetic target file: remark-inspector-target.md.

CLI

remark-config-inspector [options]
remark-config-inspector build [options]

Core options

  • --config <configFile>: explicit config file path
  • --basePath <basePath>: root path used for glob resolution
  • --file <filePath>: alias of --target
  • --target <filePath>: file used for effective config resolution
  • --files: include matched file metadata in payload (enabled by default)

Static build

To generate a static inspector snapshot:

npx remark-config-inspector build

This emits a single-page app in .remark-config-inspector.

Static build options

  • --base <baseURL>: deployment base URL
  • --outDir <dir>: output directory (default: .remark-config-inspector)

Environment variables

Primary variables:

  • REMARK_CONFIG (or legacy ESLINT_BASE_PATH)
  • REMARK_BASE_PATH (or legacy ESLINT_BASE_PATH)
  • REMARK_TARGET (or legacy ESLINT_TARGET)

Run npx remark-config-inspector --help for all options.

License

Apache-2.0

Contributors ✨

All Contributors.

Thanks goes to these wonderful people (emoji key):