GeezerVison is showing github.com — tsconfig.json does not work with VS 2015 · Issue #3124 · microsoft/TypeScript
tsconfig.json does not work with VS 2015 #3124DescriptionI am trying to give options to typescript namely trying tell how to load modules from VS. For new ASP.NET 5 templates this option simply not available, worse typescript 1.5 does not honor tsconfig.json either so what should I do ? ActivityCyrusNajmabadi commented on May 12, 2015 OnurGumus commented on May 12, 2015 Any work around for the time being? I need to specify modules to AMD. paulvanbrenk commented on May 12, 2015 No guaranteed workaround, you can try adding a TypeScriptModuleKind element to a propertygroup, with amd or commonjs specified.. not sure if that gets correctly communicated to the compiler. added this to the This milestone has been deleted milestone on May 12, 2015OnurGumus commented on May 12, 2015 Thanks that seems to work. JohnFlyIII commented on May 17, 2015 +1 for this to work in VS2015 RC without workarounds.
I really enjoy the experience from VS Code paulvanbrenk commented on May 18, 2015 This will work in the final release of VS 2015. mhegazy commented on May 19, 2015 Updating the label to suggestion as this is not a bug level change; this does not change the plan of shipping this in the next public VS release. paulvanbrenk commented on May 20, 2015 Checked in the code to enable this scenario in VS 2015 alexandero-brd commented on Nov 4, 2015 I use latest (1.6.3 TypeScript language services), VS 2015 and ASP .Net Betta8. I have FrontendApp folder in the root of web project with tsconfig.json. It contains compiler options and links to files with TS definitions. I also use WebPack + ts-loader to build frontend application and it builds successfully.
But Visual Studio code analyzer shows errors in the TypeScript files for imports of modules which are declared in the definition files. If I add references like
/// <reference path="typings/tsd.d.ts" />
then errors are disappearing. But all these files are already declared in the tsconfig.json so I don't want to have two sources of these files. What is even more interesting that I have several modules (external) and I added reference comments only to one of them (the main one). If I reopen project and open some other TypeScript file (not main) - Visual Studio shows errors. If I open main TS file after that and wait a few seconds then errors disappear (in all TS files). And after each project reopen I need to open main TS file and wait few seconds.
Is it possible just to use files list with definitions from tsconfig.json without including reference comments? paulvanbrenk commented on Nov 4, 2015 alexandero-brd commented on Nov 4, 2015 So, is it possible to use tsconfig.json in other folders (not in "Scripts")? If not - are you going to support such scenarios and when can we expect such feature? paulvanbrenk commented on Nov 4, 2015 @oryol No, not in TypeScript 1.7 (or earlier). However I'm right now working on making the tsconfig.json support a lot better in VS 2015, you should see that in the 1.8 release.
Caveat: Any features don't actually exist until they're checked-in/shipped, and schedules can change at a moments notice. alexandero-brd commented on Nov 4, 2015 defyjoy commented on Mar 6, 2016 Does this still work for *.csproj files ? I opened a new blank asp.net application and tried to make it work with tsconfig.json .The project I chose in 2015 was
But it seems the VS completely ignores the tsconfig.json.
My project structure somewhat looks like this
Note : I am using typescript v1.8.2 mhegazy commented on Mar 7, 2016 paulvanbrenk commented on Mar 7, 2016 dehghani-mehdi commented on Jan 18, 2017 Doesn't work here, I'm using VS 2015.3 and latest version of TypeScript dazinator commented on Jan 18, 2017 When using VS2015, put the tsconfig file in a "Scripts" folder. Otherwise I don't think VS will find it or honour it. dehghani-mehdi commented on Jan 18, 2017 Darrell (@dazinator) that isn't really good way to deal with config file, I always rename Script folder to js, personally prefer to use commad-line to deal with this issue. dazinator commented on Jan 18, 2017 Mehdi Dehghani (@dehghani-mehdi) - yep I know. I also think it's a poor, but that is how the VS project system (vs2015) supports typescript projects as far as I know. This should help Joydeep Roychowdhury (@defyjoy). If you want to handle typescript project compilation outside VS using tsc that will of course work. dazinator commented on Jan 18, 2017 Also - if you do decide to use command line tsc to handle typescript project compilation, then you will want to disable VS from automatically transpiling ts files to js files (as it will to do that depending on your VS configuration settings for typescript language). To prevent VS from doing this in VS2015, add the following to your .csproj file:
<TypeScriptCompileBlocked>true</TypeScriptCompileBlocked> dehghani-mehdi commented on Jan 19, 2017 Darrell (@dazinator) Thanks for the note, for now I just add tsconfig.json to the project for disabling auto generate JS file by VS :), of course the correct solution is what you mentioned.
MetadataMetadataDevelopmentNo branches or pull requestsIssue actions
|
