Add `npm browserify` command #4322

Closed
domenic opened this Issue Dec 16, 2013 · 7 comments

Comments

Projects
None yet
9 participants
@domenic
Member

domenic commented Dec 16, 2013

This has been under discussion for a while, but I wanted to log it as a work item. To make npm the best JavaScript package manager and help it crush all competition, we need to have easier first-class support for browserifying.

I am not sure what exactly the scope of this feature is. Browserify has a pretty big ecosystem; do we want to support all of it? (Transforms, watchify, etc.) How much of a burden do we end up taking on ourselves, which was previously not ours? Maybe we can just delegate entirely to browserify, and tell people to go get involved in that community---we just include it as a convenience? Are we comfortable with the speed and code quality of browserify as-is (e.g. the issue where it pretends to be streaming but instead buffers everything along each step of the way)?

@substack

This comment has been minimized.

Show comment Hide comment
@substack

substack Dec 16, 2013

Contributor

There are other competing packages for building commonjs modules and that is a good thing. People can just npm install -g browserify if they agree with how browserify does bundling. I don't think it's a good idea to bake this in to npm because npm should focus on being a package manager, not a bundler for browser code.

Contributor

substack commented Dec 16, 2013

There are other competing packages for building commonjs modules and that is a good thing. People can just npm install -g browserify if they agree with how browserify does bundling. I don't think it's a good idea to bake this in to npm because npm should focus on being a package manager, not a bundler for browser code.

@rxaviers

This comment has been minimized.

Show comment Hide comment
@rxaviers

rxaviers Dec 16, 2013

👍 with @substack

👍 with @substack

@oncletom

This comment has been minimized.

Show comment Hide comment
@oncletom

oncletom Dec 16, 2013

crush all competition

?

Making npm better, okay.
Trying to overcome every competitor, what's the point?

And actually who are the competitors? For browsers there is a lot of stuff. But they are not competitors of npm; they almost all rely on it.

crush all competition

?

Making npm better, okay.
Trying to overcome every competitor, what's the point?

And actually who are the competitors? For browsers there is a lot of stuff. But they are not competitors of npm; they almost all rely on it.

@monteslu

This comment has been minimized.

Show comment Hide comment
@monteslu

monteslu Dec 16, 2013

Way too specific for npm.

Way too specific for npm.

@tobie

This comment has been minimized.

Show comment Hide comment
@tobie

tobie Dec 16, 2013

Please don't conflate package managing with dependency management and module-bundling of client-side code.

tobie commented Dec 16, 2013

Please don't conflate package managing with dependency management and module-bundling of client-side code.

@mreinstein

This comment has been minimized.

Show comment Hide comment
@mreinstein

mreinstein Aug 8, 2014

we should close this ticket. browserify is phenomenal, I use it daily at home and work, but it doesn't belong as part of npm.

we should close this ticket. browserify is phenomenal, I use it daily at home and work, but it doesn't belong as part of npm.

@othiym23

This comment has been minimized.

Show comment Hide comment
@othiym23

othiym23 Jun 2, 2016

Contributor

Browserify is an incredibly useful workflow for many developers. However, it's not the only one, and putting it into npm directly was probably never in the cards. Beyond that, having a standard way to do builds for front-end use cases is still a good goal, but it's probably not going to get implemented as a top-level command like this. It's also not clear when the team is going to get to this, but because it's something with wide-ranging implications, and as such is something that will be done with heavy consultation with the user community. As such, I'm going to close this issue, and we'll spin up a new discussion when the team is ready to move on this. Thanks for your time!

Contributor

othiym23 commented Jun 2, 2016

Browserify is an incredibly useful workflow for many developers. However, it's not the only one, and putting it into npm directly was probably never in the cards. Beyond that, having a standard way to do builds for front-end use cases is still a good goal, but it's probably not going to get implemented as a top-level command like this. It's also not clear when the team is going to get to this, but because it's something with wide-ranging implications, and as such is something that will be done with heavy consultation with the user community. As such, I'm going to close this issue, and we'll spin up a new discussion when the team is ready to move on this. Thanks for your time!

@othiym23 othiym23 closed this Jun 2, 2016

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