The only time I see this is when installing a command-line utility of some kind. For instance, if you install express with -g you can generate an app skeleton.
Installing libraries globally would be a problem, but it doesn't seem like this is what Codebox is doing.
If you don't want global state you could use a VM?
It's global because it is not per project. For example, I don't want to install a tool in every folder that I might happen to use it in. (Or bother setting paths and symlinks)
Comments
Are they running each app in a separate container/vm? This one seems to made for desktop though.
The only time I see this is when installing a command-line utility of some kind. For instance, if you install express with -g you can generate an app skeleton.
Installing libraries globally would be a problem, but it doesn't seem like this is what Codebox is doing.
The global install is only for when you're running it locally on your machine (it isn't fully packaged for the desktop yet, but will be soon).
On our cloud service (https://www.codebox.io) we do run each app in a seperate container/VM of course.
npm install -g is more like apt-get install
If you don't want global state you could use a VM?
It's global because it is not per project. For example, I don't want to install a tool in every folder that I might happen to use it in. (Or bother setting paths and symlinks)