Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

What version of node.js or node is Visual Studio Vnext using... seems to be in conflict with my local version #393

Closed
xtianus79 opened this issue Mar 18, 2015 · 2 comments
Closed

What version of node.js or node is Visual Studio Vnext using... seems to be in conflict with my local version #393

xtianus79 opened this issue Mar 18, 2015 · 2 comments

Comments

@xtianus79
Copy link

node is - v 0.12.0
I am using 2.5.1 for npm
@xtianus79 xtianus79 changed the title What version of npm is Visual Studio Vnext using... seems to be in conflict with my local version What version of node.js or node is Visual Studio Vnext using... seems to be in conflict with my local version Mar 18, 2015
@Eilon
Copy link
Member

Eilon commented Mar 25, 2015

@DamianEdwards @madskristensen

@xtianus79
Copy link
Author

Thus was answered to .10.31 and how to update it was explained.

natemcmaster added a commit that referenced this issue Nov 13, 2018
@natemcmaster
Add more logging for flaky tests on CI (#393)
d51a695
natemcmaster pushed a commit that referenced this issue Nov 14, 2018
@davidfowl
Merge pull request #393 from benaadams/patch-1
b1a772f 
Disconnect is Debug not Error
ryanbrandenburg pushed a commit that referenced this issue Nov 19, 2018
@jbagga
Merge pull request #393 from aspnet/release/2.1
d2befa4 
Use applicationUrl instead of ASPNETCORE_URLS (#390)
natemcmaster pushed a commit that referenced this issue Nov 21, 2018
@jbagga
Add logger extensions with event ids (#405)
d22bb2c 
Addresses #393
natemcmaster pushed a commit that referenced this issue Nov 30, 2018
@jbagga
Add breakingchanges (#393)
b816b37 
Addresses #350
@ghost ghost locked as resolved and limited conversation to collaborators Dec 4, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Eilon @xtianus79