Publish to bower registry

[marcboscher]

Please publish the browserified version to the bower.io registry

[marcboscher]

Or at least, include the /dist folder with browserified output in the release file on github

[slobak]

Thanks Marc, we'll get it published.

On Sun, Jan 11, 2015 at 11:17 AM, Marc Boscher [email protected] wrote:

Or at least, include the /dist folder with browserified output in the release file on github

— Reply to this email directly or view it on GitHub https://github.com/Asana/node-asana/issues/53#issuecomment-69506838.

[slobak]

We haven't yet set up auto-publish on bower, but we now automatically publish the dist/asana.js file as part of a GitHub release:

https://github.com/Asana/node-asana/releases/download/v0.5.3/asana.js

Does that work for you?

On Mon, Jan 12, 2015 at 8:35 PM, Greg Slovacek [email protected] wrote:

Thanks Marc, we'll get it published.

On Sun, Jan 11, 2015 at 11:17 AM, Marc Boscher [email protected] wrote:

Or at least, include the /dist folder with browserified output in the release file on github

— Reply to this email directly or view it on GitHub https://github.com/Asana/node-asana/issues/53#issuecomment-69506838.

[marcboscher]

Just tried this in my bower file's dependencies and it's working

"asana": "https://github.com/Asana/node-asana/releases/download/v0.7.1/asana-min.js"

Only thing is bower will generate a .bower.json file because there's none, and obviously that generated file is a bit thin on info. But otherwise it's a good enough workaround.

#aa.commenter Marc Boscher #aa.id 27963340695629

[slobak]

Gotcha. I'm not familiar with bower enough to know, if we embed some info (e.g. export bower package metadata somewhere) in that file will bower be able to pick it up?

On Thu, Feb 26, 2015 at 1:54 PM, Marc Boscher [email protected] wrote:

Just tried this in my bower file's dependencies and it's working

"asana": " https://github.com/Asana/node-asana/releases/download/v0.7.1/asana-min.js"

Only thing is bower will generate a .bower.json file because there's none, and obviously that generated file is a bit thin on info. But otherwise it's a good enough workaround.

#aa.commenter Marc Boscher #aa.id 27963340695629

— Reply to this email directly or view it on GitHub https://github.com/Asana/node-asana/issues/53#issuecomment-76282422.

[marcboscher]

Honestly, I'm no expert. But here is an example of another dependency hosted as a GitHub release.

from my bower.json "chrome-platform-analytics" : "https://github.com/GoogleChrome/chrome-platform-analytics/archive/ca1.5.2.zip"

If you open the zip you will find an example of a bower.json pointing to its "binary" file. If instead of publishing the asana-min.js and asana.js as individual files you just zipped then with a bower.json then you'd be golden.

// Commented from Asana and synced using http://crosscheck.io

#aa.commenter Marc Boscher #aa.id 28578388378500

[slobak]

Sure, that seems pretty doable.

On Thu, Mar 5, 2015 at 1:07 PM, Marc Boscher [email protected] wrote:

Honestly, I'm no expert. But here is an example of another dependency hosted as a GitHub release.

from my bower.json "chrome-platform-analytics" : " https://github.com/GoogleChrome/chrome-platform-analytics/archive/ca1.5.2.zip "

If you open the zip you will find an example of a bower.json pointing to its "binary" file. If instead of publishing the asana-min.js and asana.js as individual files you just zipped then with a bower.json then you'd be golden.

// Commented from Asana and synced using http://crosscheck.io

#aa.commenter Marc Boscher #aa.id 28578388378500

— Reply to this email directly or view it on GitHub https://github.com/Asana/node-asana/issues/53#issuecomment-77451851.