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

high-standard

v6.0.0

Published

The hassle-free opinionated JavaScript code linter

Downloads

255

Readme

High Standard is a hassle-free opinionated JavaScript code linter powered by ESLint.

The tool automatically scans and generates ESLint configs suitable to your tool chains:

  • Git (not linting whatever in .gitignore)
  • Jasmine
  • Jest
  • jQuery
  • Lodash
  • Prettier
  • React
  • Testing Library
  • TypeScript
  • Vitest

Command-line usage

npm exec high-standard [...path] [--options]

|Argument|Description| |---|---| |path|Specify one or more file/directory/glob paths to files to be linted. If none specified, the current working directory will be used.| |--warnings or -w|Turn on rules with warning severity.| |--cache|Speed up processing time by reading last cached results.| |--fix or -f|Fix auto-fixable errors and warnings.| |--update-allowlist or -u|Silence all present errors so the next run will not report these errors again. Meaning that, as long as the error count per-file per-rule is lower or the same, the process will not break.| |--no-type-checking|Speed up processing time by disabling the rules that require type information services.| |--no-progress|Print only linting results.|

ESLint compatible usage

Importing high-standard package exposes its ESLint flat configs, therefore you can integrate this with your typical ESLint workflow.

For example,

  1. Install high-standard package locally
    npm install --save-dev high-standard
  2. Create eslint.config.js file next to your package.json containing
    module.exports = require('high-standard')
    // or if ESM
    import config from 'high-standard'
    export default config
  3. Install ESLint extension for VS Code.
  4. Expect to see linting results inside your VS Code.