Board Thread:Questions and Answers/@comment-24187005-20131124044004/@comment-24187005-20140126161459

Well, I got around this mess:

First, I set up a batch file that would wipe out the habitrpg-shared folders from node_modules and bower_components and copy in my working clone. (I also set up a less invasive batch to just change out index.coffee and habitrpg-shared.js, my most commonly edited files.)

Later, I created an Ubuntu Linux VM as a dev environment. There, the symlinking described in this article worked just fine! I have this question, though: if I run an npm install or update, or bower install/update, will that wipe out the symlink? Do I need to tell the npm and bower .json files not to touch habitrpg-shared?