After installing the July 3 dev build, I can now use NTVS again without it crashing immediately, so big improvement there.
However, the new Intellisense throws about 200 errors/warnings that I consider to be bogus (or at very least, "not helpful").
The first case of this is that it finds about 100 errors/warnings in the "express-hbs" package and a dozen or so warnings in the "azure" package (these are both reasonably common and installable from npm). Maybe these errors/warnings are legit (but I question that). But more importantly, I don't care. I don't want to see errors/warnings from included packages, particularly not hundreds of them that make it impossible for me to find/notice actual errors from my own project.
The second case, which I've reported on the some of the old bugs, is that I have the ACE code editor included in my project (as just a bunch of static files, including many JS files, that are served to browser clients). None of this JS is technically part of my Node project, but the Intellisense still roots around in there and throws 100+ errors/warnings. Now in this case, I don't doubt that there are issues in terms of that code being clean Node JavaScript (because it isn't Node JavaScript - it's browser JavaScript). So what I'd like to do is tell NTVS to ignore those files. I've tried indicating the files as not part of the project, but then they don't get distributed to my cloud service on publish.
However, the new Intellisense throws about 200 errors/warnings that I consider to be bogus (or at very least, "not helpful").
The first case of this is that it finds about 100 errors/warnings in the "express-hbs" package and a dozen or so warnings in the "azure" package (these are both reasonably common and installable from npm). Maybe these errors/warnings are legit (but I question that). But more importantly, I don't care. I don't want to see errors/warnings from included packages, particularly not hundreds of them that make it impossible for me to find/notice actual errors from my own project.
The second case, which I've reported on the some of the old bugs, is that I have the ACE code editor included in my project (as just a bunch of static files, including many JS files, that are served to browser clients). None of this JS is technically part of my Node project, but the Intellisense still roots around in there and throws 100+ errors/warnings. Now in this case, I don't doubt that there are issues in terms of that code being clean Node JavaScript (because it isn't Node JavaScript - it's browser JavaScript). So what I'd like to do is tell NTVS to ignore those files. I've tried indicating the files as not part of the project, but then they don't get distributed to my cloud service on publish.