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

Which module bundler should I use? #3

Closed
koistya opened this issue Aug 29, 2014 · 13 comments
Closed

Which module bundler should I use? #3

koistya opened this issue Aug 29, 2014 · 13 comments

Comments

@koistya
Copy link
Member

koistya commented Aug 29, 2014

Browserify

img img img img
npm
npm
img
npm

Who's using React.js with Browserify?

  • KhanAcademy.org
  • AirBnb.com
  • SoundCloud.com

Webpack

img img img img
npm
npm
img
npm

Who's using React.js with Webpack?

  • Instagram.com

Good Read

@JasonGiedymin
Copy link

When I end up using browserify with gulp, I end up using many shims and plugins. It hurts more when you have to do transpiling or if you also end up using bower. Watchify if very fast too. However, I get the sense that browserify devs recommend using it as a cli tool, and if your fine with that it actually works quite well.

@yoshuawuyts
Copy link

Browserify has a very active community behind it, and bazillion plugins that form a rich ecosystem. If you want to use gulp + browserify you should take a look at https://github.com/hughsk/vinyl-source-stream.

@sloria
Copy link

sloria commented Nov 23, 2014

+1 to webpack. It's code-splitting and ability to incorporate multiple sources (e.g. bower, node, etc) is indispensable. It boasts a long list of loaders and plugins and intelligent caching for quick builds.

@radum
Copy link

radum commented Feb 2, 2015

@sloria You can do everything you said with browserify also, and when does one need to require a CSS file in his javascript file or an image?

It's like JSX, it worked and made sense for them (FB) doesn't mean it will work for everyone else.

I think both are great, so you might as well chose the one you like and stick with it. I personally us browserify because I started with this one and it has a big ecosystem.

@mauriyouth
Copy link

+webpack, you can have multiple entry point so you can split your js bundles, and load the necessary only when you needs them.

@koistya
Copy link
Member Author

koistya commented Feb 9, 2015

@mauriyouth does it differ from what you can do with Browserify and factor-bundle?

@avevlad
Copy link

avevlad commented Feb 15, 2015

👍 webpack

@hekar
Copy link

hekar commented Apr 20, 2015

+1 webpack

@koistya koistya changed the title Webpack vs Browserify Which module bundler should I use? May 17, 2015
@amit242
Copy link

amit242 commented Jul 19, 2015

Do I need Webpack or Browserify if I'm already using gulp? I'm trying to understand if I need any of these 2 if I'm using the react-starter-kit.

@Sunil6591
Copy link

can somebody point me to some samples for using browserify with react using a MakeFile?
Thanks in advance

@cosminnicula
Copy link

What do you think about JSPM?

@blackxored
Copy link

+1 for jspm, not even a mention? 😭

@koistya
Copy link
Member Author

koistya commented Feb 21, 2016

I'm going to close this one as it's not a real issue or feature request. But feel free to continue the conversation on this thread. You're also welcome to participate in discussions on Gitter, Appear.in, or StackOverflow.

@koistya koistya closed this as completed Feb 21, 2016
langpavel pushed a commit that referenced this issue Feb 19, 2019
* Upgrade all dependencies

1. ncu --upgradeAll
4. Leave "graphql" to be "^13.2.0" that apollo packages depend on
2. Apply patch of "npx babel-upgrade" output
3. Leave only necessary babel plugins
4. Pass "yarn fix" by disabling stricter rules

* Pass "req" through GraphQL resolver context

* Through rootValue it cannot be passed from browser GraphQL access
* rm unnecessary code

* Add "Timestamp" scalar type for convinience

* rm unnecessary files

* fix: Timestamp didn't work

* npm graphql requires to be update
vercel/next.js#5238 (comment)

* Feature: Codegen from GraphQL schema and use more Flow types (#2)

* install apllo

* add apollo.config.js

* apollo codegen succeeded

* fix: updateNetworkStatus signature

* rm @flow from files not ready

* add flow-typed files

* done: Using auto-generated types works

* [email protected]+ has regression. Use ^0.88.0.

* fix: invalid GraphQL primitive types

* Add codegen script

* done: import auto-generated file

* refac: move impl for apollo-link-state to graphql dir as same as server side resolvers

* codegen and ignore eslint these files

* refactor: "networkStatus"

* feat: codegen:standalone

* refac: "OnMemoryState" is what I meant

* Improve codegen (#3)

* delete existing auto-generated types

* change script name

* ignore __generated__ folder

* wip: disallow absolute path resolving under `src` dir

* It causes disregard .js type checking under src

* fix all flow error

* modify: prevent `withStyles` drops component type

* Modify targe Node versions

* Fix build failure: Codegen before lint

* Add Node v10 LTS for build target
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