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

leosco · March 3, 2017, 1:04am

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

github.com

meteor/todos/blob/master/imports/startup/server/fixtures.js

import { Meteor } from 'meteor/meteor';
import { Lists } from '../../api/lists/lists.js';
import { Todos } from '../../api/todos/todos.js';

// if the database is empty on server start, create some sample data.
Meteor.startup(() => {
  if (Lists.find().count() === 0) {
    const data = [
      {
        name: 'Meteor Principles',
        items: [
          'Data on the Wire',
          'One Language',
          'Database Everywhere',
          'Latency Compensation',
          'Full Stack Reactivity',
          'Embrace the Ecosystem',
          'Simplicity Equals Productivity',
        ],
      },

This file has been truncated. show original

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.