cc @DanielRosenwasser and @orta, the more i look at the source code for this behavior the more it feels like this cannot be what is intended given our strong preference for node style resolution instead of classic. then again, I don't really know what went into writing that code.
but it looks wrong at first glance, bc it appears to opt in all ES20XX targets into classic module resolution... which doesnt seem like what we want??
update "Module Resolution Strategies" to reflect how TS actually works
Partially addresses https://github.com/microsoft/TypeScript/issues/39555#issuecomment-656994164
cc @DanielRosenwasser and @orta, the more i look at the source code for this behavior the more it feels like this cannot be what is intended given our strong preference for
node
style resolution instead ofclassic
. then again, I don't really know what went into writing that code.but it looks wrong at first glance, bc it appears to opt in all ES20XX targets into
classic
module resolution... which doesnt seem like what we want??