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

@sngular/lint-staged-config

v1.0.0

Published

SNGULAR's lint-staged config

Downloads

10

Readme

@sngular/lint-staged-config

Sharable lint-staged config enforcing SNGULAR style guidelines.

Getting started

Install

npm install --save-dev @sngular/lint-staged-config

Configure

With ESLint

echo "module.exports = require('@sngular/lint-staged-config');" > lint-staged.config.cjs

With ESLint & Prettier

echo "module.exports = require('@sngular/lint-staged-config/prettier.cjs');" > lint-staged.config.cjs

Hook

After that you can use husky to add a pre-commit hook to lint your code before each commit:

npx husky add .husky/pre-commit 'npx --no -- lint-staged'

Different paths for .git file and package.json

husky install must be run in the same directory as .git, but you can change directory during prepare script and pass a different directory. If your .git file and package.json are in different folders, you will have to specific the package.json directory in both the prepare script and the husky hooks.

In this example, the .git file is one level below the folder with the package.json (located at /front).

{
	"scripts": {
		"prepare": "cd .. && husky install front/.husky"
	}
}

If you had a pre-commit hook, you would need to specify the directory as follows:

# ...
cd front
npm test

Scripts

Based on the selected configuration, it will execute different actions according to the following rules:

With ESLint

  • *.{js,cjs,mjs,jsx,ts,tsx}
    • eslint --fix

With ESLint & Prettier

  • *.{js,cjs,mjs,jsx,ts,tsx}
    • eslint --fix
    • prettier --write
  • *.{md,html,css,yml,yaml}
    • prettier --write