Client accountsClient.loggingIn() Source True if a login method (such as Meteor.loginWithPassword, Meteor.loginWithFacebook, or Accounts.createUser) is currently in progress. A reactive data source.

Build Plugin Plugin.registerSourceHandler(fileExtension, handler) Inside a build plugin source file specified in Package.registerBuildPlugin, add a handler to compile files with a certain file extension. Arguments fileExtension String The file extension that this plugin should handle, without the first dot. Examples: "coffee", "coffee.md". handler Function A function that takes one argument, a CompileStep object. Documentation for CompileStep is available on the GitHub Wiki.

Anywhere cursor.observe(callbacks) Source Watch a query. Receive callbacks as the result set changes. Arguments callbacks Object Functions to call to deliver the result set as it changes

Client computation.firstRun Source True during the initial run of the computation at the time Tracker.autorun is called, and false on subsequent reruns and at other times.

Client Meteor.status() import { Meteor } from 'meteor/meteor' Source Get the current connection status. A reactive data source.

Anywhere EJSON.newBinary import { EJSON } from 'meteor/ejson' Source Allocate a new buffer of binary data that EJSON can serialize. Arguments size Number The number of bytes of binary data to allocate.

modules Though Meteor 1.2 introduced support for many new ECMAScript 2015 features, one of the most notable omissions was ES2015 import and export syntax. Meteor 1.3 fills that gap with a fully standards-compliant module system that works on both the client and the server, solves multiple long-standing problems for Meteor applications (such as controlling file load order), and yet maintains full backwards compatibility with existing Meteor code. This document explains the usage and key feature

Anywhere Meteor.release import { Meteor } from 'meteor/meteor' Source Meteor.release is a string containing the name of the release with which the project was built (for example, "1.2.3"). It is undefined if the project was built using a git checkout of Meteor.

Client Template.parentData([numLevels]) import { Template } from 'meteor/templating' Source Accesses other data contexts that enclose the current data context. Arguments numLevels Integer The number of levels beyond the current data context to look. Defaults to 1.

meteor publish Publishes your package. To publish, you must cd into the package directory, log in with your Meteor Developer Account and run meteor publish. By convention, published package names must begin with the maintainer's Meteor Developer Account username and a colon, like so: iron:router. To publish a package for the first time, use meteor publish --create. Sometimes packages may contain binary code specific to an architecture (for example, they may use an npm package). In that case, ru