Skip to content
This repository was archived by the owner on Oct 12, 2022. It is now read-only.

docs(Module Resolution): update --traceModuleResolution to --traceRes… #249

Merged
DanielRosenwasser merged 1 commit into from
Apr 14, 2016
Merged

docs(Module Resolution): update --traceModuleResolution to --traceRes… #249

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions pages/Module Resolution.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -321,7 +321,7 @@ Every time the compiler sees a relative module import in a subfolder of one of t

As discussed earlier, the compiler can visit files outside the current folder when resolving a module.
This can be hard when diagnosing why a module is not resolved, or is resolved to an incorrect definition.
Enabling the compiler module resolution tracing using `--traceModuleResolution` provides insight in what happened during the module resolution process.
Enabling the compiler module resolution tracing using `--traceResolution` provides insight in what happened during the module resolution process.

Let's say we have a sample application that uses the `typescript` module.
`app.ts` has an import like `import * as ts from "typescript"`.
Expand All @@ -336,10 +336,10 @@ Let's say we have a sample application that uses the `typescript` module.
app.ts
```

Invoking the compiler with `--traceModuleResolution`
Invoking the compiler with `--traceResolution`

```shell
tsc --traceModuleResolution
tsc --traceResolution
```

Results in an output as such:
Expand Down