Added ember-addon support via npm

[jayphelps]

Worked with @rwjblue on this. To publish to npm, you'll need ember-cli v0.0.43 that has this PR which as of this writing means canary.

[rwjblue]

👍

[rwjblue]

rm -rf dist is not needed (ember-cli clears the output dir before copying the new build in).

[fivetanley]

I feel hesitant about this. Does this mean we'll publish this package to npm without it working in browserify? That seems misleading to browserify users.

[fivetanley]

I worry about having to bump minor versions and they won't line up between bower and npm and rubygems for fixes for the ember-cli loader. My personal preference is that ember-cli stuff lives in its own place like it currently does, due to its changing nature. I would prefer the version numbers to reflect the packaging as accurately as possible.

I'm working on npm support this weekend.

Edit: I don't mean to be a downer on the effort though. Ember cli addons are great I'm just not sure this will be the right place for this from a library authoring perspective right now.

[rwjblue]

How much do you enjoy wrapper packages ?

I can't see how publishing something (where nothing exists today) can harm anyone. We can always add a separate CJS entry point in the future without breaking any compatibility.

@fivetanley - Am I understanding your argument correctly as: "we can't support everyone so we shouldn't support anyone"?

[jayphelps]

@rwjblue basically said what I was thinking as well, but I do see that there has to be a line somewhere. We can't support everything. That said, last I heard ember-cli was the de facto official so I think supporting it natively is crucial. Regarding publishing w/o CJS support, it is indeed misleading. But compare the number of ember-cli peeps vs. the number of people who would run into that.

There's also this...https://www.npmjs.org/package/ember

[rwjblue]

@jayphelps - To get ember-cli to build correctly into a nested directory you will need to update the version to 0.0.43 (which should work without other major changes).

[fivetanley]

EDIT: NVMIND LOL

[stefanpenner]

@fivetanley countless wrapper packages is the ghetto. We can role out NPM support incrementally.

[fivetanley]

So on the drive home I realized how right you all are because if worse comes to worse we could move the new lib/ember-addon-main.js file to a separate package.

Forgive my slowness. :P

[fivetanley]

👍 from me

[jayphelps]

@fivetanley

[jayphelps]

One of you maintainers should prolly be the one to npm publish. Do you guys need a ticket for a reminder or nope?

[stefanpenner]

Ticket please

[jayphelps]