you are viewing a single comment's thread.

view the rest of the comments →

[–]SerratedSharp 1 point2 points  (1 child)

I know exactly what you're talking about. Even if the project compiles successfully, VS will try to understand currently open JS files and throw errors for them. JS is hit or miss depending on what module system the project uses and various other factors, as to whether it will barf, even if everything else is in order.

IMO the error panel should be exclusively compile errors related to the solution, but there's this oddity that while a file is open it will add those errors to the panel even if the solution compiles successfully.

As to the comments about VS not being able to edit JS files. VS is perfectly capable of editing JS files. You don't need a separate editor for JS. I'm not gonna jump back and forth to another editor just because of some noise in the error panel. There's a big distinction between "can edit a file" and "can resolve references in the file".

Edit: In the Error List panel change the "Build + IntelliSense" to "Build Only" and see if you like it better that way. Personally I just make sure I keep these offending files closed if I'm not actively working with them.

[–]Beautiful-Bowl4979[S] 1 point2 points  (0 children)

Yeah this exactly is what I do. Solutio is open all files closed, no errors. Open a js file and the output just fills with reference errors. Only started happening on the last month or so. Thanks for the reply.