need for ember-browerify

This isn’t an issue so much as a question … I notice both redux and the redux-think middleware are being included as part of the normal NPM build process but wasn’t sure why you’re using browserify and your import statements are “npm:redux”, etc.

Second part of this would be … would using SystemJS be a reasonable alternative or do you prefer Browserify?

Sorry for the silly question.

[yankeeinlondon]

@dustinfarris there was a great video from a guy in Germany about his experience with SystemJS and Ember (and I know he was talking to the core team at that point). I know that a lot of people believe SystemJS is better solution outside the Ember landscape but I’m really not an expert on either. Let me see if I can dig up a link for that video though … here it is:

SystemJS, JSPM, and Ember

Came out in late 2004 so it’s a bit dated but I think many of his points are still worthy of a watch if you’re interested.

[dfreeman]

For packages distributed with UMD/globals builds, a number of addons are using ember-cli-node-assets. The addon is basically just sugar for creating a broccoli tree for an npm package and then app.importing stuff from it, without all the extra build effort and runtime machinery that Browserify requires.

To support stuff like import redux from 'redux'; you could either package a vendor-shim or try out the fancy new anonymous AMD support that landed in this ember-cli PR.