2: Collections

Meteor already sets up MongoDB for you. In order to use our database we need to create a collection, which is where we will store our documents, in our case our tasks.

You can read more about collections here.

In this step we will implement all the necessary code to have a basic collection for our tasks up and running.

2.1: Create Tasks Collection

We can create a new collection to store our tasks by creating a new file at imports/api/TasksCollection.js which instantiates a new Mongo collection and exports it.


import { Mongo } from 'meteor/mongo';
export const TasksCollection = new Mongo.Collection('tasks');

Notice that we stored the file in the imports/api directory, which is a place to store API-related code, like publications and methods. You can name this folder as you want, this is just choice.

You can delete the links.js file in this folder as we are not going to use this collection.

You can read more about app structure and imports/exports here.

2.2: Initialize Tasks Collection

For our collection to work you need to import it in the server so it sets some plumbing up.

You can either use import "/imports/api/TasksCollection" or import { TasksCollection } from "/imports/api/TasksCollection" if you are going to use on the same file, but make sure it is imported.

Now it is easy to check if there is data or not in our collection, otherwise we can insert some sample data easily as well.

You don’t need to keep the old content of server/main.js.


import { Meteor } from 'meteor/meteor';
import { TasksCollection } from '/imports/api/TasksCollection';

const insertTask = taskText => TasksCollection.insert({ text: taskText });
Meteor.startup(() => {
  if (TasksCollection.find().count() === 0) {
      'First Task',
      'Second Task',
      'Third Task',
      'Fourth Task',
      'Fifth Task',
      'Sixth Task',
      'Seventh Task'

So you are importing the TasksCollection and adding a few tasks on it iterating over an array of strings and for each string calling a function to insert this string as our text field in our task document.

2.3: Render Tasks Collection

Now comes the fun part, you will render the tasks using a Vue “data container” to feed Meteor’s reactive data into Vue’s component hierarchy. We will use the vue-meteor-tracker package for this.

Meteor works with Meteor packages and NPM packages, usually Meteor packages are using Meteor internals or other Meteor packages.

This package is already included in the Vue skeleton (meteor create --vue yourproject), so you don’t need to add it.

Now you are ready to import code from this package.

When importing code from a Meteor package the only difference from NPM modules is that you need to prepend meteor/ in the from part of your import.

First we need to add the VueMeteorTracker to the root Vue instance:


import VueMeteorTracker from 'vue-meteor-tracker';


Then we need to modify the App component to get tasks from collection: imports/ui/App.vue

  <div class="container">
      <h1>Todo List</h1>
          v-for="task in tasks"

import Vue from "vue";
import Task from "./components/Task.vue";
import { TasksCollection } from "../api/TasksCollection";

export default {
  components: {
  data() {
    return {};
  methods: {},
  meteor: {
    tasks() {
      return TasksCollection.find({}).fetch();

Meteor skeletons are secure by default, but that is not what we want right now, so let’s add autopublish package so that we can more easily prototype with out data:

meteor add autopublish

This is only for prototyping and is not something to do in any application that you are going to deploy. We’ll talk more about this in step 9.

See how your app should look like now:

You can change your data on MongoDB in the server and your app will react and re-render for you.

You can connect to your MongoDB running meteor mongo in the terminal from your app folder or using a Mongo UI client, like NoSQLBooster. Your embedded MongoDB is running in the port 3001.

See how to connect:

See your database:

You can double-click your collection to see the documents stored on it:

But wait, how my tasks are coming from the server to the client? We are going to explain this later, in the step about Publications and Subscriptons. What you need to know now is that you are publishing all the data from the database to the client. This will be removed later as we don’t want to publish all the data all the time.

Review: you can check how your code should be in the end of this step here

In the next step we are going to create tasks using a form.

Edit on GitHub
// search box