consider a package manager about snap.svg

[thefoxis]

hallelujah, yes, please. 👍

[brianleroux]

this!

[madmed88]

Bower support would be great.

[cristiandouce]

👍 on component!

[rschmukler]

+1 on component

[wwwsevolod]

bower

[tiye]

Also JAM and SPM for RequireJS and SeaJS people :)

[holmesal]

bower bower bower.

[tomByrer]

@visionmedia are you suggesting for Snap.SVG itself to be served via a Package Manager, or simply be more compatible with PMs allow JS programmers package Snap.SVG with other assets easier?

[tj]

@tomByrer for the whole thing to be comprised of N packages from one of those, so at least one community can really benefit. Otherwise they just become monolithic libs like d3, which is fine but it's not very useful and low return on the amount of code that ends up being written, especially with these kinds of libs when a lot of it is really useful elsewhere

[Siyfion]

@DmitryBaranovskiy I'm sure you are aware, but for the bower package to be available to all users, there needs to be a matching semver tag in the repo. So at the moment, it's still not actually available (via Bower at least).

[DmitryBaranovskiy]

I may be not very competent with semver, but what’s wrong with this tag: https://github.com/adobe-webplatform/Snap.svg/tree/v0.1.0 ?

[Siyfion]

@DmitryBaranovskiy Ah, well the latest bower.json is stating version v0.1.1 for which there isn't a tag (as-yet), it should be fine so long as it was registered with v0.1.0 however, perhaps I am the one getting muddled.

The bower.json is only in the dev branch at the moment, so it may be because you registered https://github.com/adobe-webplatform/Snap.svg/ as the git endpoint rather than https://github.com/adobe-webplatform/Snap.svg/tree/dev, in which case it will only appear once the dev branch has been merged-in.

Perhaps, @satazor or @sindresorhus can give you a bit more help than me..

[DmitryBaranovskiy]

Ah, right. Well then it only will be truly in the bower when 0.1.1 will be released. Which should be relatively soon.

[tomByrer]

Ah gotcha @visionmedia; you want Snap.SVG to have good modular habits from the start :)

[tj]

yea, d3 is similar in that almost all of it is super useful outside of d3. Even "silly" things like simple modules of easing functions come in handy in other places. Dmitry / Mike and friends are obviously great at this stuff :D it's just even more awesome if we can get at all the little bits when it makes sense

[mulderp]

any recent advice on snapsvg as a commonjs module? I just applied http://learnjs.io/blog/2014/02/20/using-snapsvg-with-browserify/ to have snapsvg imported via commonjs