Feature Request: use installed prettier version

Expected Behavior

I’d expect nx to use the installed prettier version for formatting.
Running prettier or nx format on the command line for the same file should yield the SAME results.

Current Behavior

Nx uses a fixed internal version of prettier and ignores the installed prettier version

Failure Information (for bugs)

Steps to Reproduce

• install nx version 8.5.0
• install prettier version 1.18.2

E.g. use else in an Angular template

<div *ngIf="someBoolean; else otherTemplate">
</div>

now the following checks should yield the same result:

$ nx format:check --files login.component.html
$ prettier -c login.component.html

But since nx version 8.5.0 uses an older version of prettier (1.16.4), the results are inconsistent.

Other

When nx uses the installed prettier version this can avoid

• confusion: e.g. Stackoverflow: prettier vs. nx format:check
• inconsistencies fix(nx): update workspace to use prettier v1.18.2
• and we can use newer prettier versions without updating nx

Notes:

• If using the installed prettier version is not possible, then maybe nx can at least show an error/warning when the installed prettier version does not match
• The nx format docs should mention that nx ignores the installed prettier version
• It would be helpful to have an nx command to print the internal prettier version

[kylecordes]

Ah, based on that above info, I think maybe this item should be titled something more like:

“Make prettier a peerDependency instead of a dependency”

I don’t know if this is a good idea or if the Nx team wants it, but it’s much more plausibly good than the earlier interpretation “use the globally installed prettier” that a bunch of us immediately dismissed.

[wKovacs64]

Personally, I would be very surprised if a project used my globally installed version of a tool rather than the package-local version. The current behavior is exactly what I would expect. Running prettier (globally installed) vs. running yarn prettier (or nx format:check in this case) mean different things. Is this more of a documentation opportunity rather than a code/behavior change?

Maybe I am in the minority here and checking for a globally installed version of something to take precedence over a package-local version is more conventional than I realize. If so, can someone point to a common/popular example of where this happens? Always happy to educate myself.

Thanks.