First, it would be to update to 1.3.2.4 (semver power, hey?) with meteor update and see what it breaks. Normally it shouldn't break a lot of things, it's a real maturity update. Here is a really good talk I saw about it: http://slides.com/shapoc/upgrade-to-meteor-13
You could then switch your app structure as recommended with the imports folder and less globals, if you feel comfortable with of course (it's not an obligation to use this pattern).
With that, you could use packages with meteor npm install my-awesome-package --save and import them with import { superFunction } from 'my-awesome-package' instead of doing Meteor.npmRequire('my-awesome-package..) (pretty old syntax!).
First, it would be to update to 1.3.2.4 (semver power, hey?) with
meteor updateand see what it breaks. Normally it shouldn't break a lot of things, it's a real maturity update. Here is a really good talk I saw about it: http://slides.com/shapoc/upgrade-to-meteor-13You could then switch your app structure as recommended with the imports folder and less globals, if you feel comfortable with of course (it's not an obligation to use this pattern).
With that, you could use packages with
meteor npm install my-awesome-package --saveand import them withimport { superFunction } from 'my-awesome-package'instead of doingMeteor.npmRequire('my-awesome-package..)(pretty old syntax!).