Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider supporting Browserify packages implicitly. #74

Open
kriskowal opened this issue Mar 18, 2014 · 2 comments
Open

Consider supporting Browserify packages implicitly. #74

kriskowal opened this issue Mar 18, 2014 · 2 comments

Comments

@kriskowal
Copy link
Member

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.

@hthetiot
Copy link
Contributor

hthetiot commented May 1, 2017

So if we do that we dont need 'mini-url' and we can also inject 'promise' I would say and remove bluebird from montage

@hthetiot hthetiot added this to the v17.1.x milestone May 1, 2017
@hthetiot
Copy link
Contributor

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants