template.subscribe

Client template.subscribe(name, [arg1, arg2...], [options]) Source A version of Meteor.subscribe that is stopped when the template is destroyed. Arguments name String Name of the subscription. Matches the name of the server's publish() call. arg1, arg2... Any Optional arguments passed to publisher function on server. Options onReady Function Passed to Meteor.subscribe. onStop Function Passed to Meteor.subscribe. connection DDP Connection The connection on which to m

this.setUserId

Server this.setUserId(userId) Source Set the logged in user. Arguments userId String or null The value that should be returned by userId on this connection.

computation.stop

Client computation.stop() Source Prevents this computation from rerunning.

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

Meteor.release

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.

audit-argument-checks

audit-argument-checks This package causes Meteor to require that all arguments passed to methods and publish functions are checked. Any method that does not pass each one of its arguments to check will throw an error, which will be logged on the server and which will appear to the client as a 500 Internal server error. This is a simple way to help ensure that your app has complete check coverage. Methods and publish functions that do not need to validate their arguments can simply run check(ar

Cordova.depends

package.js Cordova.depends(dependencies) Specify which Cordova / PhoneGap plugins your Meteor package depends on. Plugins are installed from plugins.cordova.io, so the plugins and versions specified must exist there. Alternatively, the version can be replaced with a GitHub tarball URL as described in the Cordova page of the Meteor wiki on GitHub. Arguments dependencies Object An object where the keys are plugin names and the values are version numbers or GitHub tarball URLs in string

api.export

package.js api.export(exportedObjects, [architecture], [exportOptions], exportOptions.testOnly) Export package-level variables in your package. The specified variables (declared without var in the source code) will be available to packages that use your package. If your package sets the debugOnly, prodOnly or testOnly options to true when it calls Package.describe(), then packages that use your package will need to use Package["package-name"].ExportedVariableName to access the value of an

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.