Now that we use imports, what's the proper use of Meteor.startup()?

Sort of a general question, but I’m having some trouble wrapping my head around it.

If it’s best practice to control your build/execution order using imports, what’s the proper usage of Meteor.startup()? Is it only used to perform special functions (like pre-loading data) on your collections, and nothing else? Looking at the sample todos app, the only place Meteor.startup() is used is in

Can anyone comment on how Meteor.startup() fits in with the rest of your build order? From my own testing, it looks the Meteor.startup() execution actually happens last, after the rest of your server code has been processed, but that isn’t made clear explicitly in the docs.

1 Like