When module not found, show output of `--traceResolution` for that module

TypeScript Version: latest

Code

import { x } from "unresolved-module";

Expected behavior:

Shows the attempts to resolve "unresolved-module".

Actual behavior:

Just says that the module wasn't resolved.

People can always turn on --traceResolution after getting such an error, but that shows the resolution for all modules, which can be pretty long.

[mhegazy]

It is strange that you get a punch of trace messages with your errors.. i wounder if there is a way to just say trace resolutions for failed modules..

[DanielRosenwasser]

traceResolution: boolean | "maybe" 😄

[mhegazy]

or --traceResolution "myModule"

[aluanhaddad]

This would be an extremely valuable and very much appreciated feature.

[pirtim]

For future lurkers - rather obvious - workaround:
tsc --traceResolution | grep 'unresolved-module'

[RyanCavanaugh]

Not much feedback on this, and the module resolution trace is extremely verbose and not formatted for everyday usage. I'm honestly not sure it would even help, since if the module is present, the trace doesn't explain why it didn't look in the place you expected it to be found.