Possible dist /build step to build a bower component with browserify? about react-router HOT 7 CLOSED

I'm slightly familiar with the --standalone flag, but I'm not sure how it handles third-party dependencies. We depend on a couple libs like es6-promise and querystring, does it bundle those up?

from react-router.

Also, the react ecosystem seems to favor cjs. I have spent countless hours on the module/package manager front in JavaScript and I am happy to end the tears and just ship cjs until other, more patient people make es6 happen as seamlessly as the cjs+npm+browserify workflow.

If you get something working, feel free to own a shim repo on bower with the same name as the npm registry. If its automated well enough we could look into adding to our release script.

from react-router.

Thanks for hearing me out - I decided to punt and go w/ jspm as I can use the ES6 loader they have along with any number of different formats like CJS (using npm for this module) and ES6 for others I'm using / etc

from react-router.

Just an update (I know this issue is closed but it's worth updating for those that might follow)

I did get this working -the full ES6 example below (bower / es6 / react / react-nested-router / karma)

https://github.com/toranb/react-es6-routing-example

from react-router.

I'm not opposed to this, I'll take a closer look soon.

from react-router.

It's still using React and this project as globals (right now) but it's nice to have ES6 as an option

from react-router.

+1

I agree that this would be nice. I tend to keep my vendor and app files separate, and by being forced to trace the dependencies all the way through via browserified npm includes it tends to mix concerns and unnecessarily increase build time. Also, a single dist file would also allow the lib to be more portable like @toranb mentions above in reference to Bower.

(Also, @toranb, just saw your comment above -- could you remove your package from the Bower registry if it indeed does not work?)

from react-router.