allow mixing --project command line parameter with a list of files, includes, and exclludes #12958

Activity

1. Ryan Cavanaugh (RyanCavanaugh)

   added

   In DiscussionNot yet reached consensusNot yet reached consensus

   SuggestionAn idea for TypeScriptAn idea for TypeScript

   on Dec 16, 2016
2. zpdDG4gta8XKpMCd commented on Dec 16, 2016

   

   ZpdDG4gta (zpdDG4gta8XKpMCd)

   on Dec 16, 2016

   Author

   More actions

   case 1: multiple entry points to the application

   I have 11 entry points (topmost scripts to start execution from), so i need to generate 11 different bundles using outFile which requires me to create and support 11 different configs

   tsconfig.a.json
   tsconfig.b.json
   tsconfig.c.json
   tsconfig.d.json
   tsconfig.e.json
   tsconfig.f.json
   tsconfig.g.json
   tsconfig.h.json
   tsconfig.i.json
   tsconfig.j.json
   tsconfig.k.json
   tsconfig.l.json
   tsconfig.m.json
   tsconfig.o.json
   

   and we are planning to add 27 more
3. zpdDG4gta8XKpMCd commented on Dec 16, 2016

   

   ZpdDG4gta (zpdDG4gta8XKpMCd)

   on Dec 16, 2016

   Last edited by zpdDG4gta8XKpMCd

   Author

   More actions

   case 2: compiling a sub-tree of all files based on compilerOptions from tsconfig.json

   another use case, for the sake of saving some time i want to compile a only sub-tree of our 1500+ project starting at given root file, yet using the compilerOptions from the tsconfig.json
4. timocov commented on Feb 5, 2019

   

   Evgeniy Timokhov (timocov)

   on Feb 5, 2019

   Contributor

   More actions

   Related #29241 (comment)

   TL;DR: paths compiler option cannot be passed via CLI.
5. RyanCavanaugh commented on Aug 21, 2019

   

   Ryan Cavanaugh (RyanCavanaugh)

   on Aug 21, 2019

   Member

   More actions

   Let's track at #27379
6. Ryan Cavanaugh (RyanCavanaugh)

   closed this as completedon Aug 21, 2019