Skip to content
Permalink
Browse files

Docs: Fix the format option name in the document (#13770)

  • Loading branch information
ganta committed Oct 20, 2020
1 parent 84fd591 commit b0257953be704d0bb387fc15afd7859fd6f19ba5
Showing with 2 additions and 2 deletions.
  1. +2 −2 docs/developer-guide/working-with-custom-formatters.md
@@ -11,7 +11,7 @@ module.exports = function(results) {
};
```

To run ESLint with this formatter, you can use the `-f` (or `--formatter`) command line flag:
To run ESLint with this formatter, you can use the `-f` (or `--format`) command line flag:

```bash
eslint -f ./my-awesome-formatter.js src/
@@ -50,7 +50,7 @@ The [Using Rule metadata](#using-rule-metadata) example shows how to use the `da

## Packaging the Custom Formatter

Custom formatters can also be distributed through npm packages. To do so, create an npm package with a name in the format of `eslint-formatter-*`, where `*` is the name of your formatter (such as `eslint-formatter-awesome`). Projects should then install the package and can use the custom formatter with the `-f` (or `--formatter`) flag like this:
Custom formatters can also be distributed through npm packages. To do so, create an npm package with a name in the format of `eslint-formatter-*`, where `*` is the name of your formatter (such as `eslint-formatter-awesome`). Projects should then install the package and can use the custom formatter with the `-f` (or `--format`) flag like this:

```bash
eslint -f awesome src/

0 comments on commit b025795

Please sign in to comment.
You can’t perform that action at this time.