Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Document usage of putout with a single rule or plugin

See original GitHub issue

Issue Description

How can I use putout to apply a single rule, such as remove-unused-variables?

It would be helpful if there was a simple, documented approach for this. Ideally, it should be possible to do this with a single command and without creating a .putout.json file.

It seems that specifying a limited set of rules or plugins in the local .putout.json file does not by default disable rules or plugins specified in the default putout.json file. That is, it seems that the local plugins are added to the default, instead of replacing them. For the rules, it appears as though certain rules are on by default (even without appearing in the default .putout.json file) and I have not found a comprehensive list of all rules.

Using putout --disable-all source.js seems to only disable rules which are currently violated in the source files being evaluated, not all rules comprehensively.

Further, the documentation seems to be somewhat redundantly duplicated between the top level readme and the readme in the putout package which I find confusing.

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:8 (8 by maintainers)

github_iconTop GitHub Comments

oprogramadorcommented, Sep 4, 2020

putout example.js --no-config --plugins remove-unused-variables works fine, thanks

coderaisercommented, Sep 3, 2020

Add ability to run desired plugins from command line without config in v9.13.0 🎉

putout example.js --no-config --plugins remove-unused-variables

Is it works for you?

Read more comments on GitHub >

github_iconTop Results From Across the Web

GitHub - coderaiser/putout
Putout is JavaScript Linter, pluggable and configurable code transformer based on Babel with built-in ESLint. It has a lot of transformations that keeps ......
Read more >
Rules | Bazel
Typically, output attributes are only used when a rule needs to create outputs with user-defined names which cannot be based on the target...
Read more >
Command Line Interface - ESLint - Pluggable JavaScript Linter
A pluggable and configurable linter tool for identifying and reporting on patterns in JavaScript. Maintain your code quality with ease.
Read more >
Apache Maven Dependency Plugin – Usage
Multiple artifacts can be defined in a single execution. A default output directory is specified but can be overridden for each ArtifactItem ...
Read more >
Use Logstash to stream logs with pipeline transformations via ...
Microsoft Sentinel's new Logstash output plugin supports pipeline transformations and advanced configuration via Data Collection Rules ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Post

No results found

github_iconTop Related Hashnode Post

No results found