Skip to content
This repository has been archived by the owner on Mar 23, 2023. It is now read-only.

Browserify in examples #68

Closed
EvanCarroll opened this issue Sep 29, 2014 · 6 comments
Closed

Browserify in examples #68

EvanCarroll opened this issue Sep 29, 2014 · 6 comments

Comments

@EvanCarroll
Copy link

If it's not needed. yank it! I think some of these examples are needlessly complex.

@fisherwebdev
Copy link
Contributor

Browserify helps us do modular development in the browser with the CommonJS module system. It will also do the JSX and ES6 transpilation for us. As such, it has a lot of value, and to some extent, the code depends on it.

The examples were written not only to show people how to use Flux, but also to point the way toward "best practices". JSX, CommonJS and ES6 are, in my opinion, best practices for Flux. I don' t want to recommend other package managers or module systems, as I believe that npm and CommonJS are currently the best options that the open source community has.

If at some point we decide to switch from CommonJS to ES6 modules, then we'll update all the code that is helping us with CommonJS.

However, I do understand that this may be a barrier for some folks, and I'd happily entertain a more fleshed out idea for a new, extremely basic example for newcomers. Please let me know what were the biggest hurdles for you, and we can take a look at what we could do to make things easier.

@briandipalma
Copy link

I can't imagine large scale Web app development without using a module system and loader. It would be a step back to remove those. If people find those complex their use case might not need patterns like flux, a simpler approach might be as productive.

@EvanCarroll
Copy link
Author

There is nothing in the docs about it. I had to grep bundle.js to find mention as a comment in a separate example that it dealt with Browserify. I still have no idea what Browserify does or why it's needed.

Backbone for example doesn't this at all -- and flux is supposed to be a replacement, no?

@briandipalma
Copy link

Maybe the documentation needs to mention that the examples use a CJS loader. You can use either Browserify or WebPack and if you don't know what they are I recommend spending some time reading up on them. Do you still load all your JS/CSS etc by creating script and link tags? That's painful to scale so you might find these module loaders helpful.

@cirocosta cirocosta mentioned this issue Oct 1, 2014
@totty90
Copy link

totty90 commented Oct 2, 2014

Here is an example: https://github.com/totty90/jogabo-flux-react

@fisherwebdev
Copy link
Contributor

I would consider the Flux TodoMVC tutorial to be a core part of the documentation, and Browserify, bundle.js, etc. are clearly explained there. I do apologize that this was difficult for you. But I encourage you to give it another try! It really is a nice way to work, once you get it set up.

In the mean time, I'll put together another, even simpler example very soon.

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

No branches or pull requests

4 participants