Closed GA-MEB closed 8 years ago
So, as it turns out, problems between node 4 and node-debug are common. Actually, problems between node 4 and various important libraries are common! Here's the proposed solution:
nvm install 0.12
nvm use 0.12
nvm alias default v0.12
Source: https://github.com/FreeCodeCamp/FreeCodeCamp/issues/3146
@MattB-GA-Boston do we need node-inspector?
@laurenfazah Are you getting an error?
In js-template
it may depend on other wiring.
Sorry, it shouldn't be a problem for js-objects
. If it is, please let me know.
@ga-wdi-boston/core I believe this was related to using node 5 prematurely in WDI 009. Can this be closed or re-scoepd as a discussion about using node-inspector?
@jrhorn424 node-inspector is a debugger interface that runs in chrome (for a node app). We haven't been using it, but it might make sense since they'd have a consistent interface for debug tools.
On the other hand, they might not be able to easily decouple browser from server.
@ga-wdi-boston/core Thoughts? (rescoepd :-P.)
Double checked, not getting these install errors. I'll leave it up to you two to decide where this issue stands otherwise :) @gaand @jrhorn424
I'm ok with closing. I'm not sure the value for using node-inspector
when compared to the potential conflation between browser and server.