Build system

The Meteor build system is the actual command line tool that you get when you install Meteor. You run it by typing the meteor command in your terminal, possibly followed by a set of arguments. Read the docs about the command line tool or type meteor help in your terminal to learn about all of the commands. What does it do? The Meteor build tool is what compiles, runs, deploys, and publishes all of your Meteor apps and packages. It’s Meteor’s built-in solution to the problems also solved by tool

template.data

Client template.data Source The data context of this instance's latest invocation.

template.view

Client template.view Source The View object for this invocation of the template.

Accounts.emailTemplates

Server Accounts.emailTemplates import { Accounts } from 'meteor/accounts-base' Source Options to customize emails sent from the Accounts system.

reactiveVar.set

Client reactiveVar.set(newValue) Source Sets the current value of the ReactiveVar, invalidating the Computations that called get if newValue is different from the old value. Arguments newValue Any

App.info

App.info(options) Set your mobile app's core configuration information. Options id, version, name, description, author, email, website String Each of the options correspond to a key in the app's core configuration as described in the Cordova documentation.

Meteor.isCordova

Anywhere Meteor.isCordova import { Meteor } from 'meteor/meteor' Source Boolean variable. True if running in a Cordova mobile environment.

appcache

appcache The appcache package stores the static parts of a Meteor application (the client side Javascript, HTML, CSS, and images) in the browser's application cache. To enable caching simply add the appcache package to your project. Once a user has visited a Meteor application for the first time and the application has been cached, on subsequent visits the web page loads faster because the browser can load the application out of the cache without contacting the server first. Hot code pushes ar

Tracker.Dependency

Tracker.Dependency A Dependency represents an atomic unit of reactive data that a computation might depend on. Reactive data sources such as Session or Minimongo internally create different Dependency objects for different pieces of data, each of which may be depended on by multiple computations. When the data changes, the computations are invalidated. Dependencies don't store data, they just track the set of computations to invalidate if something changes. Typically, a data value will be acco

Meteor.methods

Anywhere Meteor.methods(methods) import { Meteor } from 'meteor/meteor' Source Defines functions that can be invoked over the network by clients. Arguments methods Object Dictionary whose keys are method names and values are functions.