Gotcha - unfortunately implementing the solution explorer UI wouldn't wouldn't be as simple as enabling it for other project types because NTVS is based on MPFProj, which is a different project system than the rest of Visual Studio. Additionally, things could start getting out of hand if we begin messing with other project types that we don't test - I'm unconvinced it would be worth the time investment. We also don't want to unnecessarily clutter other project types.
That said, we might be able to enable the npm install dialog and the .npm command in the interactive window for non-NTVS projects. Would that be sufficient?
As far as making it work for other project types in the future, if you give me a better idea of why you'd want to use a node module elsewhere - why is this a valuable/common scenario to support? - it'll give me something to forward it on to another team and see if they might be interested in working with us to support that scenario (a real "user request" would be weighted more highly than my own contrived scenario :-) )
That said, we might be able to enable the npm install dialog and the .npm command in the interactive window for non-NTVS projects. Would that be sufficient?
As far as making it work for other project types in the future, if you give me a better idea of why you'd want to use a node module elsewhere - why is this a valuable/common scenario to support? - it'll give me something to forward it on to another team and see if they might be interested in working with us to support that scenario (a real "user request" would be weighted more highly than my own contrived scenario :-) )