Skip to content

Conversation

billti
Copy link
Member

@billti billti commented Feb 12, 2016

The actual module resolution algorithm was still falling back to classic if the module kind wasn't specified explicitly in the settings. This fixes that (and impacts a lot of tests in the process).

{ name: "noErrorTruncation", type: "boolean" },
{ name: "suppressOutputPathCheck", type: "boolean" }
{ name: "suppressOutputPathCheck", type: "boolean" },
{ name: "moduleResolution", type: "string"}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

do we need this, I think that moduleResolution will already work since it is legal command line option

@vladima
Copy link
Contributor

vladima commented Feb 13, 2016

👍 to change modulo question in harness.ts

billti added a commit that referenced this pull request Feb 13, 2016
…edModuleKind

Fix module resolution falling back to classic
@billti billti merged commit 977adde into master Feb 13, 2016
@billti billti deleted the fixNodeResolutionForUnspecifiedModuleKind branch February 13, 2016 02:05
@microsoft microsoft locked and limited conversation to collaborators Jun 19, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants