Description
Search Terms
tsconfig js tsconfig programatically
Suggestion
I would like for TypeScript to add suport for tsconfig.js instead of tsconfig.json (similar to what babel/jest/prettier have.
Use Cases
I have some alias.js file which contains an object with all of my aliases which I then import on 3 different places: babel.config.js , webpack.config.dev.js, webpack.config.prod.js. (In case it is not obvious, this is a CRA ejected project).
I then want to be able to use VSCode navigation capabilities but I cannot because he does not find the aliases. After some research I believe you could create a tsconfig.json which VSCode would then look for the paths there and make path resolution work (plus vs-code would not complaint about unresolved module errors from eslint).
If I was able to do a tsconfig.js file I would be able to fix this and vscode would then just read from that file automatically.
Checklist
My suggestion meets these guidelines:
- [ X ] This wouldn't be a breaking change in existing TypeScript/JavaScript code
- [ X ] This wouldn't change the runtime behavior of existing JavaScript code
- [ X ] This could be implemented without emitting different JS based on the types of the expressions
- [ X ] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, etc.)
- [ X ] This feature would agree with the rest of TypeScript's Design Goals.