BrowserProvider: strictly for the browser?

[fauxbytes]

Is there anything barring a node program from using a BrowserProvider? or its predecessor - a Web3Provider? Should such usage be avoided?
Thanks

[ricmoo]

Not really, if you have a node-based EIP-1193 provider, the BrowserProvider can wrap it. That's just currently a rare situation. Are there any you know of? Or are planning to write? :)

The name BrowserProvider was chosen just to make it more obvious as to its common usage. The old Web3Provider was originally intended for wrapping a Web3.js provider, and its evolving API, but once Web3.js moved to EIP-1193, that became moot.