Skip to content

Commit 3716a57

Browse files
committed
Correct eslint-path-formatter usage within README
As stated in Bartvds/eslint-path-formatter#2 the correct usage of the `eslint-path-formatter` plugin is `.pipe(eslint.format('node_modules/eslint-path-formatter'));`.
1 parent 443dd48 commit 3716a57

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -257,7 +257,7 @@ eslint.format('checkstyle')
257257

258258
// use the "eslint-path-formatter" module formatter
259259
// (@see https://github.com/Bartvds/eslint-path-formatter)
260-
eslint.format('eslint-path-formatter')
260+
eslint.format('node_modules/eslint-path-formatter')
261261
```
262262

263263
The `output` argument may be a `WritableStream`, `Function`, or `undefined`. As a `WritableStream`, the formatter results will be written to the stream. If `undefined`, the formatter results will be written to [gulp’s log](https://github.com/gulpjs/gulp-util#logmsg). A `Function` will be called with the formatter results as the only parameter.

0 commit comments

Comments
 (0)