nodejstools

> So there's an example of node-specific problem and there doesn't seem to be any impetus surrounding solving it. ??? There's so little impetus around solving it that both sides(npm and Microsoft) have put in significant effort to do it - npm 3 reduced the chance of having a very large path, and preview builds of the .net file api are removing the MAX_PATH limit. https://github.com/Microsoft/nodejstools/issues/69 https://github.com/Microsoft/nodejs-guidelines/blob/master/w...

It looks like they're working on it and it's supported in the latest Node Tools releases? https://github.com/Microsoft/nodejstools/issues/77#issuecomm...

Windows to this day still has the 260 chars path limit. http://msdn.microsoft.com/en-us/library/aa365247(VS.85).aspx... https://en.wikipedia.org/wiki/Long_filename Microsoft should finally fix such old limitations (-> update WinAPI), instead adding work arounds to third party projects like Nodejs. https://github.com/Microsoft/nodejstools/issues/69 They could also improve the command line shell (cmd.exe) that also PowerShell relies on.

Also, visual studio community edition is free[1] can debug nodejs with an extension[2]. And the capability is integrated into VS Code[3] which works cross-platform. Those and webstorm/intellij are the ones I have experience with. But most of the time, I just use the CLI debugger -- it's not hard. [1] https://www.visualstudio.com/en-us/products/visual-studio-co... [2] https://github.com/Microsoft/nodejstools [3] https://code.visualstudio.com/

That's what we call software engineering and object-oriented design - a tale of two classes from the same project cooked by Microsoft: class ProjectNode 6076 lines (5116 sloc) 274.992 kB https://github.com/Microsoft/nodejstools/blob/master/Common/Product/SharedProject/… class ProjectTypeDefinition 30 lines (27 sloc) 1.388 kB https://github.com/Microsoft/nodejstools/blob/master/Common/Product/SharedProject/… Two extremes in the same project, sitting side-by-side in the same folder on a disk. Can't imagine a valid reason for such abominations to exist. Anyway, we have the R# nowadays to simplify the refactoring.

Whoa totally did not expect to see this hit HN! dev/person-in-video here, happy to answer any questions we couldn't get to in the video :) GitHub repo for those interested in playing around with the code. https://github.com/Microsoft/nodejstools

Exciting progress, and I'd love to use it, but the thing holding me back is lack of support for ES6 syntax. https://github.com/Microsoft/nodejstools/issues/77

Dev here, happy to answer any questions. GitHub link: https://github.com/Microsoft/nodejstools