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

lint-recently

v0.2.2

Published

lint recently git commited files

Downloads

5

Readme

lint-recently

Like lint-staged, but run linters against recently modified git files by times.

Why

These days more and more projects are constructed as monorepo, and some non-monorepo projects are really big. so run lint on the full project spend very long time again and again.

Yes, we can use lint-staged before git commit to lint files partically, but git hooks can be skipped. So many bad code can still be in your codebase.

Then we can run lint-recently in CI/CD, and find out if someone bad guys skip the git hooks and pollute our codebase.

Usage

lint-recently

Command line flags

Usage: lint-recently [options]

Options:
  -V, --version                      output the version number
  -c, --config [path]                path to configuration file, or - to read from stdin
  --cwd [path]                       run all tasks in specific directory, instead of the current
  -d, --debug                        print additional debug information (default: false)
  -p, --concurrent <number|boolean>  the number of tasks to run concurrently, or false for serial (default: true)
  -q, --quiet                        disable lint-recently’s own console output (default: false)
  -r, --relative                     pass relative filepaths to tasks (default: false)
  -v, --verbose                      show task output even when tasks succeed; by default only failed output is shown (default: false)
  -x, --shell [path]                 skip parsing of tasks for better shell support (default: false)
  -h, --help                         display help for command

Configuration

configuration will be loaded in these files in order.

  • .lintrecentlyrc.json
  • lint-recently object in package.json

Options supported are list below

  • days, integer, we will use git diff between the latest commit and ${days} days ago's commit to find all modified files. Default to 3.
  • patterns, like lint-staged options in .lintstagedrc.json. Patterns should be an object where each value is a command to run and its key is a glob pattern to use for this command

.lintrecentlyrc.json example

{
  "$schema": "./node_modules/lint-recently/dist/lib/schema.json",
  "days": 3,
  "patterns": {
    "*.{ts,tsx,js,jsx}": ["eslint"]
  }
}

License

MIT