ESLint Inferred Task Options

[patrickhousley]

It seems like inferred tasks are not built on top of their non-inferred counterpart or does not make use it's executor. For example, for eslint, if you use an inferred task, it runs eslint binary directly instead of making use of the eslint executor. This means some of the options like --print-config does not work for inferred tasks. And I don't think this is the first time I have seen this. I guess the question here, or maybe the feature ask, is that inferred tasks build or make use of the already built out executors. Was there a reason that was not done?

[Tungsten78]

The inferred task will route any argument you provide to the underlying tool.

So yes, print-config should work as it did before.

nx run project-with-inferred-task:lint --printconfig <file>
or add to options override in nx.json or project.json

One big advantage of the inferred task over the executor is there is no longer a need to explicitly map each argument directly. Every argument of eslint --help is now available to you.

nx show project project-with-inferred-task outlines this nicely