Permit specification of 1.8 compiler options on properties page for Visual Studio projects

[NoelAbrahams]

I would like to specify some of these options via the settings for a Visual Studio project.

--noImplicitReturns.
--noFallthroughCasesInSwitch
--allowJs

Currently, this is not possible:

I am aware that VS now supports .tsconfig. Is that going to be the only way forward?

[mhegazy]

have you considered using a tsconfig.json?

[NoelAbrahams]

@mhegazy, as I said at the end of the post I was thinking along the same lines. But I'm not sure how tsconfig.json is going to play with NTVS projects. Are you pushing tsconfig.json as the comprehensive solution going forward?

[paulvanbrenk]

tsconfig.json should work with all project types... if you run into issue I would love to hear about them.

NTVS projects was one of the reasons for broader tsconfig.json support, that way you can contain both the client- and server-side javascript in the same project, but use different settings for both.

[mhegazy]

tsconfig.json is where we would like the configuration to live moving forward. it is easier to edit and understand for most JS developers, and cheaper to change for us (vs. the property pages UI); also works well with other tools in the build chain.

[NoelAbrahams]

@paulvanbrenk,@mhegazy, that's good to hear. We have some dependencies on the old _references.ts that we need to rewrite, before switching to tsconfig. I'll let you know how things go.

I'm also glad that NTVS is being taken into account on par with TypeScript development. Their project seems to be slowly lapsing into oblivion and as TypeScript moves forward, it's a bit worrying. There is no good alternative in Visual Studio for developing, testing and debugging TypeScript NodeJS projects. If you are privy to any information on this, I think a lot of people would be interested.

[mhegazy]

No "lapsing into oblivion", I would assure you. and we do care about our NodeJS developers. it is just hard to keep updating the UI for the property pages for every option added to the compiler, and tsconfig should solve that moving forward.

[NoelAbrahams]

I was referring to the lack of commits in the NTVS github project - not to the commitment on the TypeScript side (which of course is exceptional). There are a few key issues that have not been resolved on the NTVS side (such as this one microsoft/nodejstools#223, which has been open since June last year).

[mhegazy]

that is what i meant :). @mousetraps can add more.

[mousetraps]

Hey @NoelAbrahams. @mhegazy is correct - in fact, we are actually in the midst of growing the team! The fact is, however, that we do have a very small core team, can only do so many things at any given time, and unfortunately much of the work that we have been doing lately is not externally visible. That said, your post prompted me to consider potential opportunities to improve communication going forward, so I really appreciate your feedback and would love for you to be involved in this discussion 😃. microsoft/nodejstools#677

[jslew]

The problem for me is that the presence of tsconfig.json seems to shut off VS2015's "Compile On Save" option, despite the fact that it is not really a compiler-level option. So it's seemingly impossible to get "Compile On Save" and "AllowJs" at the same time without manually firing up an external "tsc --watch".

[mhegazy]

Compile on Save while you have a tsconfig.json is disabled by default, to enable it go to tools\options\Text Editor\TypeScript\Project and check "Automatically compile typescript files which are not part of a project". note that there is no way in TS 1.8 beta to disable/enable it for a single tsconfig.json file. With #2326, which should be in the next TS 1.8 release should have a property ("compileOnSave") to enable/disable Compile on Save in tsconfig.json.

[jslew]

Thanks for the tip. That will work even if the files are part of the csproj?
On Feb 3, 2016 4:39 PM, "Mohamed Hegazy" [email protected] wrote:

Compile on Save while you have a tsconfig.json is disabled by default, to
enable it go to tools\options\Text Editor\TypeScript\Project and check
"Automatically compile typescript files which are not part of a project".
note that there is no way in TS 1.8 beta to disable/enable it for a single
tsconfig.json file. With #2326
#2326, which should be in
the next TS 1.8 release should have a property ("compileOnSave") to
enable/disable Compile on Save in tsconfig.json.

—
Reply to this email directly or view it on GitHub
#6767 (comment)
.

[mhegazy]

Starting with 1.8.2, setting "compileOnSave" in your tsconfig should enable/disable the feature for this tsconfig.json file.

[mhegazy]

see https://github.com/Microsoft/TypeScript/wiki/tsconfig.json#compileonsave

[NoelAbrahams]

@mhegazy, the original problem was not to do with compile-on-save; it was to permit all compiler options to be settable via the setting page. As it stands it doesn't make much sense.

Why not just have a free text box so that users can set what they like?

[paulvanbrenk]

@NoelAbrahams not sure what you mean with a free text box? But I am working on an easier to maintain properties page, so adding changes will be easier in the future.

[NoelAbrahams]

Just a text box to enter any compiler option that one may want, e.g.

This just gets passed to the compiler.

I'm not sure if this is great UX, but at least it'll get the job done.

[mhegazy]

json files provide a similar experience, and most js devleopers are already familiar with its syntax. so my recommendation still stands.

[NoelAbrahams]

Well, yes, we'll probably migrate to using the json config at some point ourselves. My point had more do to with leaving behind a half complete settings page.