Server this.connection Source Access inside the publish function. The incoming connection for this subscription.

Client Blaze.getView([element]) import { Blaze } from 'meteor/blaze' Source Gets either the current View, or the View enclosing the given DOM element. Arguments element DOM Element Optional. If specified, the View enclosing element is returned.

Event Maps An event map is an object where the properties specify a set of events to handle, and the values are the handlers for those events. The property can be in one of several forms: eventtype Matches a particular type of event, such as 'click'. eventtype selector Matches a particular type of event, but only when it appears on an element that matches a certain CSS selector. event1, event2 To handle more than one type of event with the same function, use a comma-separated list. The hand

Client template.find(selector) Source Find one element matching selector in this template instance. Arguments selector String The CSS selector to match, scoped to the template contents.

Client computation.invalidate() Source Invalidates this computation so that it will be rerun.

less LESS extends CSS with dynamic behavior such as variables, mixins, operations and functions. It allows for more compact stylesheets and helps reduce code duplication in CSS files. With the less package installed, .less files in your application are automatically compiled to CSS and the results are included in the client CSS bundle. If you want to @import a file, give it the extension .import.less to prevent Meteor from processing it independently.

meteor list Lists all the packages that you have added to your project. For each package, lists the version that you are using. Lets you know if a newer version of that package is available.

After reading this article, you’ll know: About npm and Atmosphere, two JavaScript package systems you can use with Meteor How to use npm packages and deal with callback-based APIs How to use Atmosphere packages in your Meteor application Building an application completely from scratch is a tall order. This is one of the main reasons you might consider using Meteor in the first place - you can focus on writing the code that is specific to your app, instead of reinventing wheels like user login

Anywhere EJSON.isBinary(x) import { EJSON } from 'meteor/ejson' Source Returns true if x is a buffer of binary data, as returned from EJSON.newBinary. Arguments x Object The variable to check.

Anywhere customType.clone() Source Return a value r such that this.equals(r) is true, and modifications to r do not affect this and vice versa.