Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Node.js Tools for Visual Studio

blogs.msdn.com

Post reply on HN
Print view View original

31–40 of 127 posts

Re: Node.js Tools for Visual Studio

#31

Post by nickysielicki »

untog wrote: post #28
nickysielicki wrote: post #26

Earlier quoted context omitted.

I wasn't ever trying to say this is a bad effort or anything. I think it's a relatively good thing. I just don't see azure as sustainable.

Why not? Azure is platform agnostic at this point, it isn't just a home for .NET code.

The same reason I use *nix on the desktop: I like to be able to poke around on everything.

It's really scary for someone new, but power users like environments where everything is modifiable and hate GUIs.

I like being able to configure nginx a certain way. I like being able to get into a psql shell and play around with my data. I don't want to just give someone a git repository and magically press some buttons in their UI and have it work, because when you inevitably realize you want to do something special, you're stuck.

Re: Node.js Tools for Visual Studio

#32

Post by twerquie »

matthewowen wrote: post #25

I know this doesn't really mean anything, but it's kinda funny that this is at v1.0, but node.js is at version 0.12.1

It does mean something, that Node.js has a backwards version numbering scheme. That's one of the first things the io.js people corrected in their fork (they are strict semver and started at 1.0.0).

Re: Node.js Tools for Visual Studio

#33

Post by blawa »

nickysielicki wrote: post #9

How many people do you think will actually use this? I just really cannot ever see mass use of azure and visual studio in the web ecosystem. The people writing nodejs code are all using vim and unix, and you're asking them to give up their workflow and change operating systems. I want to be able to poke around in bash. (edited back in) Sure, some people new to web programming might go this route. But the next big web…

Have you heard of something called sampling bias? Not long ago there was a comment where someone mentioned Macs are whats used everywhere, lol

Re: Node.js Tools for Visual Studio

#34

Post by AdeptusAquinas »

MichaelGG wrote: post #16
mousetraps wrote: post #2

Dev here - happy to answer any questions you have :)

Wow this looks pretty amazing! How do you handle the super-long paths npm is so fond of? On Windows I often run into issues when searching or trying to manipulate a solution containing anything npm due to too-long paths.

I have run into this problem as well. Manually modifying packages is not fun.

Re: Node.js Tools for Visual Studio

#36

Post by dahart »

mousetraps wrote: post #2

Dev here - happy to answer any questions you have :)

Ooh, tracepoints, DO WANT! Are they only available in one of the paid versions of Visual Studio?

The VS debugger is excellent, its probably the dev tool I miss the most since leaving C++ and going to JS, and tracepoints are the feature I wish for most frequently in a browser debugger.

So I was about to naively suggest the VS team could push for tracepoints in IE, but OMG! Tracepoints are in IE11. Where have I been? In prejudice-land. This might mean I have to open my mind and use IE for dev, though the bias runs wide, I still might have to use it in secret for a little while, at least at work. ;)

Re: Node.js Tools for Visual Studio

#37

Post by mousetraps »

MichaelGG wrote: post #16
mousetraps wrote: post #2

Dev here - happy to answer any questions you have :)

Wow this looks pretty amazing! How do you handle the super-long paths npm is so fond of? On Windows I often run into issues when searching or trying to manipulate a solution containing anything npm due to too-long paths.

We try to mitigate the issue in a few ways:

1) warnings when you hit max_path that offer to run 'npm dedupe'

2) sometimes that doesn't work, so we also suggest people start their projects in a short path like c:\src (embarassing, I know)

3) patiently await a flat node_modules directory - http://blog.npmjs.org/post/111968476155/npm-weekly-6

4) groan very loudly when it happens - no good keeping those emotions bottled up ;-)

luckily #1/#2 cover most cases

Re: Node.js Tools for Visual Studio

#38

Post by WorldWideWayne »

MichaelGG wrote: post #16
mousetraps wrote: post #2

Dev here - happy to answer any questions you have :)

Wow this looks pretty amazing! How do you handle the super-long paths npm is so fond of? On Windows I often run into issues when searching or trying to manipulate a solution containing anything npm due to too-long paths.

I use a tool called flatten-packages [1] and I usually do all of my npm work while visual studio is closed (and use short root paths as mousetraps suggested). I just flatten them after adding/updating/syncing packages.

[1] https://www.npmjs.com/package/flatten-packages

Re: Node.js Tools for Visual Studio

#39

Post by 0xFFC »

robwilliams wrote: post #22
nickysielicki wrote: post #9

How many people do you think will actually use this? I just really cannot ever see mass use of azure and visual studio in the web ecosystem. The people writing nodejs code are all using vim and unix, and you're asking them to give up their workflow and change operating systems. I want to be able to poke around in bash. (edited back in) Sure, some people new to web programming might go this route. But the next big web…

node.js has been used heavily inside Microsoft for quite some time so even if they created this for internal use only it wouldn't be a waste of time. Microsoft employee here. And I think you vastly underestimate how popular Visual Studio is among enterprise developers - they're doing web development as well.

I don't have access to anyone inside of Microsoft, So I bring this up here, please tell Microsoft to develop official ssh client (With server it would be even better, but for now client I think would be enough) , I am tired of using putty for SSH'ing into my virtual machine. (or at least they can fork putty and make it official).Even in git plugin in visual studio they developed there is no SSH support.

Re: Node.js Tools for Visual Studio

#40

Post by mousetraps »

egeozcan wrote: post #35
mousetraps wrote: post #2

Dev here - happy to answer any questions you have :)

Any chance that it'll support Babel (known previously as 6to5) + JSX (The react extensions to JavaScript)? I love Visual Studio and I also love to write ES6 - I don't want to choose.

make a feature request! we're a small team, so we have to prioritize - generally the policy is to build what people want. works well enough :)

https://nodejstools.codeplex.com/workitem/list/basic

Post reply on HN