Disable all rules about putout HOT 4 CLOSED

The thing is the rules putout has is best practices, and it is recommended to use it. So yes, there is a difference with eslint, that it should have most rules enabled to keep your code base in best quality it can be :).

Anyways, there is an option --disable-all, which will disable all rules that was found by putout running on your codebase and save configuration into .putout.json. So you don't need to apply all rules putout suggest's and after setting baseline you can benefit from putout small suggestions while you writing new code.

It can look this way:

putout . --disable-all

from putout.

Thanks, that seems to help. I still disagree about default rules thought. Rules will always be subjective and will never suit everyone. The only sane default for such tools is a empty default ruleset, allowing advanced users to configure exactly what they need. Beginners can just extend your base config.

from putout.

I’m understand what you talking about and want to mention that the idea of least configuration is just what you said: advanced users that knows what they want can configure only what the need, for least experienced developers defaults is preferred, so they do not need to configure anything (creating same files again, and again) and keep codebase in a very good state.

There is also putout API, where you can choose only things that needed with:

const {code} = putout(‘const a = “hello”’, {
    fix: true,
    plugins: [
        ‘convert-commonjs-to-esm’
    ]
});

This code will run only one chosen plugin.
Here is examples of using:

• in mock-import
• in cloudcmd

About eslint handling things, there is a couple differences:

• putout changes behaviour of changed code;
• putout has progress bar;
• all plugins of putout is modules;
• there is no warnings, only errors;
• plugins api much simpler;
• testing api has test descriptions, and have ability to skip, and put only (any count);
• all plugins are fixable;
• there is processors, that supports extending to support all kinds off files you ever need;

So yes, there is a lot differences, and this is the reason this project exists :).

from putout.

@silverwind there is simplified way of converting Commonjs to ESM exists, and ability to disable all options for CLI :).

from putout.