EJSON.newBinary

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.

AccountsClient#logout

Client accountsClient.logout([callback]) Source Log the user out. Arguments callback Function Optional callback. Called with no arguments on success, or with a single Error argument on failure.

modules

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

Selectors

Mongo-Style Selectors The simplest selectors are just a string or Mongo.ObjectID. These selectors match the document with that value in its _id field. A slightly more complex form of selector is an object containing a set of keys that must match in a document: // Matches all documents where deleted is false {deleted: false} // Matches all documents where the name and cognomen are as given {name: "Rhialto", cognomen: "the Marvelous"} // Matches every document {} But they can also contain mo

spiderable

Your JavaScript code can run in two environments: the client (browser), and the server (a Node.js container on a server). For each function in this API reference, we'll indicate if the function is available just on the client, just on the server, or Anywhere. Meteor Core Anywhere Meteor.isClient import { Meteor } from 'meteor/meteor' Source Boolean variable. True if running in client environment. Anywhere Meteor.isServer import { Meteor } from 'meteor/meteor' Source Boolean va

Blaze.getData

Client Blaze.getData([elementOrView]) import { Blaze } from 'meteor/blaze' Source Returns the current data context, or the data context that was used when rendering a particular DOM element or View from a Meteor template. Arguments elementOrView DOM Element or Blaze.View Optional. An element that was rendered by a Meteor, or a View.

Accounts.sendEnrollmentEmail

Server Accounts.sendEnrollmentEmail(userId, [email]) import { Accounts } from 'meteor/accounts-base' Source Send an email with a link the user can use to set their initial password. Arguments userId String The id of the user to send email to. email String Optional. Which address of the user's to send the email to. This address must be in the user's emails list. Defaults to the first email in the list.

Contribution guidelines

Please submit clarifications and improvements to the Guide! If it’s just a small fix, go ahead and open a PR. If it’s something more major, please file an issue for discussion first. Using the change log If you are adding significant new content, please take a moment to include an update to the changelog in your PR. Writing tips Things to be aware of: Always use specific IDs on headers so that we can change them later: // bad ## Using schemas with collections // good <h2 id="schemas-with-co

computation.onInvalidate

Client computation.onInvalidate(callback) Source Registers callback to run when this computation is next invalidated, or runs it immediately if the computation is already invalidated. The callback is run exactly once and not upon future invalidations unless onInvalidate is called again after the computation becomes valid again. Arguments callback Function Function to be called on invalidation. Receives one argument, the computation that was invalidated.

this.onStop

Server this.onStop(func) Source Call inside the publish function. Registers a callback function to run when the subscription is stopped. Arguments func Function The callback function