Dan Dascalescu
Developer Advocate at Google. Meteor.js engineer. Founded Blueseed, the startup community on a ship.
Packaging 3rd party libraries PROPERLY
Dan Dascalescu / @dandv
2014-Dec-04
This talk's interactive
slides.com/dandvd
Show of hands
Has anyone used Bootstrap?
K, how about Moment.js?
Alright,
Font Awesome?
Atmosphere situation
The problems with these packages
(where do I start)
Out of date
Let's flag this baby !
The old 'mrt' days
Let's flag this baby !
When it's not the authors...
Let's flag this baby !
mrt add bootstrap
...is gone
You must remember
meteor add mizzao:bootstrap-3
There's a better way
the
original!
Fork
(and submit a PR)
Who's in?
- momentjs:moment
- fortawesome:fontawesome
- d3js:d3
- twbs:bootstrap
- summernote:summernote
- hammer:hammer
- keyboardjs:keyboardjs
What do we get?
Same-day updates
straight from the source
No more outdated wrapper packages
(that's where your flagging comes in!)
Atmosphere versioning
Minifying/
concatenating/
bundling
Offline/
intranet/
https
Nothing beats "straight from the author"
Paves the way for reactivity
Meteor-specific features
...and builds Meteor awareness
Takeaways
You can do it!
Atmosphere namespace
Ask @dandv for namespaces!
Star official packages
<clap/>
Packaging 3rd party libraries PROPERLY
By Dan Dascalescu
Packaging 3rd party libraries PROPERLY
Meteor's Atmosphere is currently pollutes with many outdated versions of Meteor wrappers for 3rd party libraries. Here's how to clean it up.
