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

yet-another-eslint-blame

v0.0.3

Published

Yet another eslint blame (might) with better adaptability. The input is eslint's output with json format (You can see it [here](https://eslint.org/docs/user-guide/formatters/#json)). And it's will run git blame for each eslint report.

Downloads

221

Readme

yet-another-eslint-blame

Yet another eslint blame (might) with better adaptability.
The input is eslint's output with json format (You can see it here). And it's will run git blame for each eslint report.

Install

pnpm install yet-another-eslint-blame

Usage

Before all

We have to cd into the repo's directory to read git histories.

Read eslint json output from file

  1. Run eslint and output with json:
    eg: Run eslint src -f json -o ./a.json
  2. run yet-another-eslint-blame:
    eg: Run yaeb ./a.json
  3. Enjoy!

Read eslint json output with stdin

  1. Run eslint and output with json, and pipe into yet-another-eslint-blame:
    eg: Run eslint src -f json | yaeb
  2. Enjoy!

Output with markdown todo list

With -f markdown, we will output something like:

- [] [<file and line number with the relative path>](./<file and line number with the relative path>) @<author>

It will looks like:

You can just copy it into gitlab's merge requests or issues.

Options

| name | type | default | description | |--------------------|------------------|---------|--------------------------------------| | --format or -f | json or markdown | json | Generate json or markdown todo list. | | --output or -o | string | | Specify output into a file. | | --warn or -w | boolean | false | Includes warning message. | | --suppressed or -s | boolean | false | Includes suppressed message. | | --rule or -r | string | | Specify a rule Id. | | --groupby or -g | rule | rule | Specify group by what. |