Consider supporting Browserify packages implicitly.
kriskowal opened this issue · comments
Certain Node.js core modules are reflected in npm by the eponymous package. These usually support use in browsers, e.g., url
and util
. Consider linking these packages implicitly if a package has a module that depends on them. One factor to consider is where these packages would reside, since they would have to be embedded in mr
to have a reliably location relative to any installed package. Otherwise, we could provide a warning at run-time instructing the user to install the dependency with npm in the application package or convince the package depending upon the module to include it in their own dependencies.
So if we do that we dont need 'mini-url' and we can also inject 'promise' I would say and remove bluebird from montage