Nah, I think installing locally is more common and often recommended. But I personally like the convenience of executing ad hoc bits of js on my laptop using `node` or `nodemon`. Why not the same for browser javascript?

E.g. you could do something like:

  cd ~/Desktop/foo
  npm i somepkg
  echo console.log(require('somepkg')()) > index.js
  jetpack

And now you're running some pkg in the browser, to try/test it out. That's what the use case for this feature really is. For real apps, I install it locally as well or else a breaking change in the future could cause issues.