I developed an ember-cli addon that works fine. My addon is a project by itself with a dummy site to test it, a couple of unit tests etc.

When I run the command ember build --production, it basically creates a vendor.js file that contains my addon and all dependencies (bower_components such ember, jquery etc…) which is about 2MB.

I’d like to know if it’s possible to export the addon on its own (vendor.js) without any dependencies inside, just as a vendor I can use? My main project that is using this addon already have ember, jquery… so I don’t want that to be duplicated.

I’m basically trying to make my ember-cli addon a component that I can include in multiple ember projects. My addon and all dev dependencies are more than 100MB of data (including node modules, express, broccoli, tests…), so when I run the command npm install my-addon in my main project, it installs everything (including dev dependencies, tests etc…) which is pretty big. I don’t really need that in my other project, the addon itself (dist version) should be only couple of KB and that’s all I need…

All you should need to do is include the addon into your consuming ember-cli app’s package.json (possibly via npm install --save-dev my-addon-name) as described in http://www.ember-cli.com/#discovery. Installing in this way should not result in the addon’s dev dependencies being re-downloaded or included into the consuming app.

@tilix I think you should add bower_components, node_modules etc to your .gitignore so that it doesn’t get checked in to github. Now, when your main project fetches this addon from devDependencies, there will be no bower_componets, node_modules in your final build.