Repository navigation
rooDir does not seems to work with JS files #2974
Description
I have following structure
└───src
├───external
│ └───lib
└───App
├───Class
src/external/lib/ contains 2 files, lib.js and lib.d.ts.
In src/App/Class/Class.ts I am importing ../../external/lib/lib and it works fine, but generates following structure:
└───dist
└───App
├───Class
With JS files in dist/App/Class. My config is:
{
"compilerOptions": {
"module": "commonjs",
"sourceMap": false,
"target": "ES5",
"noImplicitAny": true,
"outDir": "./dist",
"rootDir": "./src"
},
"files": [
"src/main.ts"
]
}So I thought what rootDir property should solve this problem and transfer entire structure to dist folder. Am I doing something wrong?
Activity
mhegazy commentedon Apr 30, 2015
The compiler does not copy files. I would add a post build task to copy your dependencies into the output folder.
The issue
--rootDiris solving is consistenlly identifiing the root of your files. with out the flag, it is the logest common path of all inputs, that means that something like:the output structure without
--rootDirwill look like:with no way of making
Appshow up.--rootDir .\srcwill cause App to be generated.NekR commentedon Apr 30, 2015
Mohamed Hegazy (@mhegazy) Yep, I originally structured it in a way where external dependencies are living in separate top level folder and
srcfolder contains same tree inexternalsub-folder with only.d.tsfiles, but it really feels uncomfortable to have such duplicated structure. So I thought--rootDirmight resolve this, sorry if I misunderstood its intention.Windows command
treemade it for me. Actually it's not quite useful for big tree since it does not have level parameter :(mhegazy commentedon Jun 12, 2015
Looks like this is addresses. please reopen if there is missing information.