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-staged-editorconfig

v0.1.0

Published

Integrate .editorconfig with lint-staged

Downloads

343

Readme

lint-staged-editorconfig

Test staged files are covered by editorconfig rules using lint-staged.

Quick Start

First, install:

$ yarn add -D lint-staged-editorconfig

Second, run lint-staged-editorconfig under a catch all rule in lint-staged:

{
  "lint-staged": {
    "*": "lint-staged-editorconfig"
  }
}

Third, create an .editoconfigignore to ignore files:

$ echo "vendor" >> .editorconfigignore

Why this project?

If a repo uses editorconfig, then all files in the repo should be covered by rule in it. If not, then code style goes out of sync resulting in confusion among the team.

If a new file is introduced to SCM, then it should be committed unless covered by editorconfig rules.

So, if uncovered files may be rejected from commits, then it's not possible to introduce uncovered files into SCM.

This ensures the .editorconfig covers all files in SCM and that teams do not need to rely on ad-hoc configuration of an individuals editor.