Create Please Enable Issues Tab

[dandv]

Saw this package on Atmosphere at https://atmospherejs.com/aramk/d3

How does it compare to existing d3 wrappers like https://atmospherejs.com/garrilla/d3 ?

[aramk]

I find it's usually a better idea to fork the original package rather than use submodules or worse copy it directly, because it allows you to modify the script to support Meteor (if necessary) and you can still pull upstream new versions from the main branch without having to re-apply your changes. See http://www.meteorpedia.com/read/Packaging_existing_Libraries.

[dandv]

@paralin has argued quite convincingly that it's even better than wrapping to use meteor-bower whenever possible.

Atmosphere is indeed full of abandoned wrapper packages.

[aramk]

I definitely agree with that argument. The only packages from users on atmosphere should be their own packages, not wrapped ones with minor differences. I'll give meteor-bower a try at some point. I suppose using npm for server-side dependencies rather than using meteor wrappers around them would also be a good idea.

[dandv]

Hey @aramk - I'm submitted an official PR to @mbostock, see MeteorCommunity/discussions#14 (comment)

Maybe time to unpublish this package?

meteor admin set-unmigrated aramk:d3

Thanks!

[dandv]

d3js:d3 now has 9 stars. Would you like to unmigrate aramk:d3?

[dandv]

BTW, I think it was your idea that forking is even better than submodules, that led me to write the now quite popular Official Meteor integration thread, which brought us direct integrations from Moment.js, and (almost there), Font-Awesome and d3. Thank you.

[aramk]

That sounds like a good idea, I'll unmigrate now. Thanks for your efforts.