Urban dictionary describes it best as "Worshiping someone/something that was once great and worth worshiping, but has now lost its greatness.". In this talk we uncover the truth about the saga of the Meteor.js package manager Atmosphere.

1. Atmosphere Packages
and the Chuck Norris Effect

3. 🔗 https://atmospherejs.com

5. Why Atmosphere?
● Depend on core Meteor packages, such as
ddp and blaze
● Explicitly include non-javascript files e.g.
CSS, static assets
● Use Meteor’s build system to auto-transpile
from e.g. CoffeeScript
● Ship different code for client / server,
enabling different behavior in each context

6. Why Atmosphere?
● Direct access to Meteor’s package
namespacing and package global exports
without having to explicitly use ES2015 import
● Enforce exact version dependencies using
Meteor’s constraint resolver
● Include build plugins for Meteor’s build system
● Include pre-built binary code for different
server architectures (Linux, Windows, ..)

7. https://guide.meteor.com/using-atmosphere-packages.html

9. ��

11. ��

12. Chuck Norris doesn't need try-catch, exceptions are too afraid to raise

13. 🤦

15. We can do better than that!

16. Lessons learned
● Double-check your (Meteor package) dependencies!
○ Check the GitHub repository
○ When was the last release?
○ Is it just a wrapper for an npm package?
○ Does it provide Meteor specific functionality?
● Look for alternatives, one famous example:
○ ostrio:flow-router-extra
● You might not need Atmosphere - check on npm as well, e.g.:
○ Bootstrap
○ Fontawesome
○ Moment.js
○ Fullcalendar

17. Thanks for listening
P.s: if you are looking for a cool job,
we are hiring 👐 kromit.at