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 🙏

© 2025 – Pkg Stats / Ryan Hefner

wmc-prettier-linter

v0.1.9

Published

- Node.js >= 18.0.0 - VS Code (for all features) - npm >= 7.0.0

Readme

Overview

This project uses ESLint and Prettier to ensure a consistent code style. ESLint is a linter that will analyze your code and report any errors. Prettier is a code formatter that will ensure that your code is formatted consistently. The combination of these two tools will ensure that your code is both well-written and well-formatted across your entire team.

Prerequisites

  • Node.js >= 18.0.0
  • VS Code (for all features)
  • npm >= 7.0.0

Format on Save is only available with VS Code right now if the recommended extensions are installed.

Installation

Be shure you are in the root directory of your project.

Install the package with:

npm install wmc-prettier-linter -D

Hook Installation

If you want to abort the commit if there are any errors, you can install a pre-commit hook that will run ESLint and Prettier before each commit.

  • npm run wmc-hook-install

You can also uninstall the hook by typing:

  • npm run wmc-hook-delete

ATTENTION!

If you have just warnings, the commit will be successful.

If you want to commit with errors, use

  • git commit --no-verify

Gratulations!

Now, your code is automatically checked while you write and formatted after save (recommended extensions needed). Upon committing the code to GitHub, all modified files are rechecked. If any issues are found during the check, the code commit is aborted, and errors are reported.

Lint and Fix

You can also manually check your code by entering:

  • npm run wmc-lint

or autofix your code by typing:

  • npm run wmc-fix

in your terminal.

To fromat your code (if you are not using VS Code) type:

  • npm run wmc-format

Install Recommended VS Code extensions

  • MAC: CMD + Shift + p
  • WIN: STRG + Shift + P

and enter "Show Recommended Extensions" to get a list of recommended extensions

or

  • install ESLint for VS Code here-->

    • formatting fixable ESLint errors on file save
  • install Prettier for VS Code here-->

    • formatting code (e.g. indentation) on file save
  • (optionally) install Pretty Typescript Errors for VS Code here-->

    • if using typescript, you get more readable Errors Information inside VS Code