Cookie named '' is not set!

Managing brew’s Node Versions

Is it reasonable to use brew to switch between node versions (some projects require LTS, avoids nvm)?

I realize I could just force the link but I don’t want to break anything?

Is the issue only going to present itself when I run brew upgrade? I guess I could make sure that node is linked every time before I upgrade? Does brew do this automatically?

Why would I want “the software first in my path”?

 

Leave a Reply

Your email address will not be published. Required fields are marked *