Why wrap npm modules as ember addons

@webPapaya wrote:

Hi,

I'm maintaining an Ember application and I'm a bit confused about the reason why there are so many Ember wrapping addons like:

• https://github.com/stefanpenner/ember-moment
• https://github.com/thefrontside/ember-introjs
• https://github.com/ef4/ember-browserify
• https://github.com/babel/ember-cli-babel

Is there any good reason why Ember doesn't use plain npm and bower packages and wrap those things instead? Isn't the maintenance afford a real pain, because every time a new version of one of the dependencies is released the wrapper also needs to be updated? eg. ember-cli-babel hadn't been updated in 10 months. Since then lot's of things have been added to babel-core, which users of ember can't really enjoy. Some might argue: "It's open source, you can always fork and fix it", but if ember would just use the plain npm packages it would be much simpler to update dependencies. Just change version number in your package.json

In genral I understand the concept of wrapping dependencies and normally this really makes sense, but in the code I own and not a 3rd party library. Normally this wrapper in my code base is a simple module/class which delegates calls to the library, but for me an ember addon is not lightweigt as ember addon hello-world generates more than 40 files and downloads more than 240mb (npm3 140mb) of dependencies

Thanks in advance for explaining this design decision.

Posts: 2

Participants: 2

Read full topic