module_resolution.yml
module_resolution.yml
| Name | About | Labels | Assignees |
|---|---|---|---|
| Module resolution | Report a problem with module resolution |
Module resolution can be very difficult to configure correctly!
Be sure you've read the docs and asked for help in other places before filling out this form.
Most module resolution bug reports are actually misconfigurations, so we require a thorough pre-investigation before we can look into any potential issues.
Many module problems can be automatically detected with Are The Types Wrong? and you should use this tool first if it appears that the module shape is wrong.
Let's make sure you're ready to file a module resolution bug.
A module resolution bug requires five things:
- A module that's trying to import some target module
- That target module
- The configuration of the importing module
- The configuration of the target module
- A difference in runtime behavior
You will also be required to post a cloneable repository. This repo must involve running tsc, not a third-party tool (e.g. vue-tsc, ngc, expo, ...)
Post a cloneable repo that reproduces the issue. We will run npm, yarn, or pnpm here, but will not invoke more complex build scripts or other build tools.
This should be at most four lines of code, and come from your demo repo.
Repros that depend on running within external tools (yarn, pnpm, esbuild, etc.) are not TypeScript defects and will not be investigated.
Run tsc --traceResolution and paste the output here.