You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
rootDir option documentation incorrect and confusing #22039
I've recently started a new project with TS and run into some confusing behaviour. I've placed my files in an "app" folder, but the emitted TS (using AMD modules with --outFile) generates module names without the app prefix, breaking my JS references.
Turns out that I was supposed to use rootDir, instead of rootDirs.
The first issue is that since #5819, this actually does affect outFile as well, so the documentation clearly stating it only applies to outDir is wrong.
The second issue is that it's really confusing the difference between rootDirs and rootDir, and it's still unclear to me why rootDirs: ["./"] did not produce the same result as rootDir: "./". The written documentation is not very clear out this and potentially, one or both options neeed renaming.
rootDir and rootDirs have completely different meanings... I apologize for the bad choice of names. but that said. i am not sure what part of the docs you would like to be updated? can you elaborate? also PRs would be welcomed.
Activity
[-]rootDir option documentation confusing[/-][+]rootDir option documentation incorrect and confusing[/+]mhegazy commentedon Mar 10, 2018
rootDirandrootDirshave completely different meanings... I apologize for the bad choice of names. but that said. i am not sure what part of the docs you would like to be updated? can you elaborate? also PRs would be welcomed.shadow-light commentedon Oct 11, 2018
Thanks for pointing this out! Just lost a lot of time because I thought -rootDirs was an alternative to specifying multiple --rootDir options.
Renaming would be helpful!