Share via


Repeated Warning: "The javascript language service has been disabled for the following projects..."

Question

Wednesday, November 15, 2017 10:51 PM

I cannot get the message "The javascript language service has been disabled for the following projects" to go away.  Please tell me how to disable the JavaScript language service.  I already tried playing with the tsconfig.json file for a half an hour.  It made a much bigger mess.  I just want to turn off the language service as I don't think I need it.  I just need the small amount of typescript we have in our 10 year old project to compile like it did last week before I upgraded. 

If this is not possible, please advise how I might downgrade to version 15.1 or so.  Thank you.

All replies (8)

Wednesday, November 15, 2017 11:27 PM

I keep getting the warning: the javascript language service has been disabled for the following projects

ever since I upgraded to 15.4.3.  I tried upgrading to 15.4.4 and it still has the problem.  I asked support if I could downgrade back to 15.4.1 but they said I can only go back one version.  How in the world do I get Visual Studio to work.  I have told our team to stop upgrading.


Thursday, November 16, 2017 9:08 AM

Hi 2r0y,

Thank you for posting in MSDN forum

Please try with following to troubleshoot.

Please open Windows Explorer, and navigate to  <Visual Studio Installation Path>\Common7\IDE (by default is C:\Program Files (x86)\Microsoft Visual Studio\2017\**(edition)\Common7\IDE ), and run the following commands:

devenv.exe /resetuserdata , it will take a couple of minutes to run as Visual Studio cleans up and sets itself back to its original state.

>>If this is not possible, please advise how I might downgrade to version 15.1

Currently there is no 15.1 available from official site, only VS 2017 15.0 from :https://my.visualstudio.com/Downloads?q=visual%20studio%202015&wt.mc_id=o~msft~vscom~older-downloads

Best Regards,

MSDN Community Support
Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [email protected].


Thursday, November 16, 2017 4:02 PM

Unfortunately, that did not stop the problem from happening.  Is there any way to simply turn off the yellow warning message that keeps showing at the top of visual studio?  I don't care if the JavaScript language service is disabled.  I only want it to stop moving my text down by a line while I'm trying to edit programs.  This is extremely counter-productive.


Thursday, November 16, 2017 4:42 PM | 1 vote

I believe the problem is now temporarily solved for me but it appears to require the combination of two things:

1) perform the "devenv.exe /resetuserdata" as specified above.

2) Go to Tools -> Options -> Text Editor -> JavaScript/TypeScript -> Language Service -> General
and uncheck the box: "Enable the new JavaScript language service.*"

There is probably a way to get it to work using a carefully crafted set of tsconfig.json files, but I was unable to get my typescript to compile after working with it for more time than I expected to spend.  I think that the typescript compiler may have been in disagreement with VS.  I got the VS message to go off, but I could no longer get a good build.  We are currently removing TypeScript from our codebase so the best thing for me was to turn off the JavaScript language service until that is complete.

There is a thread on StackOverflow that may be helpful on this topic.


Thursday, November 16, 2017 6:21 PM

Never mind.  The warning message comes back even when the language service is turned off and the user data has been reset.  I guess I will have to be annoyed until I find a better option.  This is really not very helpful.


Thursday, November 16, 2017 7:39 PM

After more experiments, I discovered that it appears to have something to do with the fact that some of our developers are still using VS 2015.  For that reason we are continuing to use the TypeScript 1.8 compiler until we upgrade everyone to 2017.  When I set the TypeScript version to "Use latest available" the JavaScript language service warning message goes away. When I use a tsconfig.file that excludes certain libraries.  When I go back to TypeScript 1.8, even an empty tsconfig.file will cause the message to return.

Evidently, VS 2017 doesn't work very well with TypeScript 1.8 it appears.  Unfortunately, we weren't planning to upgrade that at this time.  I may have difficulty encouraging developers to upgrade VS at this point.


Tuesday, November 21, 2017 9:31 AM

Hi 2r0y,

Thank you for your update about the cause of this issue.

If the developers upgrade VS to 2017, you could also refer to Updating TypeScript in Visual Studio 2017 to using latest available version of TypeScript.

Best Regards,

MSDN Community Support
Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [email protected].


Wednesday, November 29, 2017 1:43 AM

Hi 2r0y,

What about this issue now?

Other community members also meet this kind of issue before. If possible, please try the following steps.

(1) Update your VS2017 to the latest 15.4.5 version.

(2) Run the command line:

devenv.exe /resetuserdata

View the result.

A similar case which also provided other suggestions, reference:

https://stackoverflow.com/questions/42990428/turning-off-language-service-disabled-error-message-in-vs2017

Actually other community members also reported this issue to the product team:

https://developercommunity.visualstudio.com/content/problem/134660/the-javascript-language-service-has-been-disabled-1.html

If still no help, you could also add your comment and vote it in above feedback.

Sincerely,

Jack

MSDN Community Support
Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [email protected].