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-stdout

v0.0.6

Published

Because wtf would you have --stdin and not --stdout…

Downloads

15

Readme

eslint-formatter-stdout

npm install eslint-formatter-stdout

Does this work?

cat $PATH_TO_FILE | eslint --format stdout --stdin --fix-dry-run --stdin-filename $PATH_TO_FILE

No.

Well, does this work?

cat $PATH_TO_FILE | eslint --format eslint-formatter-stdout --stdin --fix-dry-run --stdin-filename $PATH_TO_FILE

No.

Does this package work at all?

Yeah, but not like you want it to. Why? Who knows. But if you set --format to the fully qualified path of the formatter index.js it works.

cat $PATH_TO_FILE | eslint --format "$PATH_TO_NODE_MODULES/eslint-formatter-stdout/src/index.js" --stdin --fix-dry-run --stdin-filename $PATH_TO_FILE

Why do you have to do something stupid like this? Idk—take it up with eslint. Their docs indicate that it automatically looks in node_modules for packages starting with eslint-formatter-.

But how do I see the linting errors and warnings?

Literally every other formatter does that. If you don't have a use for printing the linted code to stdout instead you're in the wrong place.