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

eslint-formatter-fix-dry-run

v1.0.0

Published

Outputs fixed file content to stdout; for use with --fix-dry-run

Downloads

13

Readme

eslint-formatter-fix-dry-run

Custom eslint formatter whose only output is file content after running fixes. This formatter is intended for use with eslint's --fix-dry-run flag which emits fixed file content in the command output instead of modifying files in place.

If you run eslint on a file that it is configured to ignore then this formatter will produce no output.

This formatter works best when eslint is applied to one file at a time. If you fix multiple files at a time then file contents in stdout will be separated by null characters (\0).

Install with,

$ yarn add --dev eslint-formatter-fix-dry-run

Why

Running eslint --fix is ever so handy. You can use that command to apply formatting with prettier if you have the prettier plugin set up, and to fix other problems at the same time.

But sometimes you don't want to modify files in place. For example if you want to use git-format-staged to fix files in a pre-commit hook it's important that the eslint command sends fixed file content to stdout. Eslint has a --fix-dry-run option that almost does this, but you need to use a custom formatter to read fixed output. The stock json formatter works, but to get fixed file content you need to pipe output to jq or another program that can parse JSON. That makes writing fixing scripts tricky if you don't want to assume that users will have jq installed.

Eslint-formatter-fix-dry-run outputs fixed file content to stdout, and nothing else, so you don't need any extra processing.