{{ loggingIn }} Source Calls Meteor.loggingIn().

Templates {{> Template.dynamic template=template [data=data] }} Source Choose a template to include dynamically, by name. Arguments template String The name of the template to include. data Object Optional. The data context in which to include the template.

{{ currentUser }} Source Calls Meteor.user(). Use {{#if currentUser}} to check whether the user is logged in.

After reading this article, you’ll know: When to create an npm package and when to create an Atmosphere package The basics of writing an npm package The basics of writing an Atmosphere package How to depend on other packages, both from Atmosphere and npm How an Atmosphere package can integrate with Meteor’s build system The Meteor platform supports two package systems: npm, a repository of JavaScript modules for Node.js and the browser, and Atmosphere, a repository of packages written specifi

webapp The webapp package is what lets your Meteor app serve content to a web browser. It is included in the meteor-base set of packages that is automatically added when you run meteor create. You can easily build a Meteor app without it - for example if you wanted to make a command-line tool that still used the Meteor package system and DDP. This package also allows you to add handlers for HTTP requests. This lets other services access your app's data through an HTTP API, allowing it to easil

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

After reading this article, you’ll know: What features in core Meteor enable user accounts How to use accounts-ui for a quick prototype How to use the useraccounts family of packages to build your login UI How to build a fully-featured password login experience How to enable login through OAuth providers like Facebook How to add custom data to Meteor’s users collection How to manage user roles and permissions Features in core Meteor Before we get into all of the different user-facing accounts

After reading this guide, you’ll know: How to build reusable client side components in any user interface framework. How to build a style guide to allow you to visually test such reusable components. Patterns for building front end components in a performant way in Meteor. How to build user interfaces in a maintainable and extensible way. How to build components that can cope with a variety of different data sources. How to use animation to keep users informed of changes. UI components In Met

After reading this guide, you’ll know: The role URLs play in a client-rendered app, and how it’s different from a traditional server-rendered app. How to define client and server routes for your app using Flow Router. How to have your app display different content depending on the URL. How to construct links to routes and go to routes programmatically. Client-side Routing In a web application, routing is the process of using URLs to drive the user interface (UI). URLs are a prominent feature

Client Tracker.onInvalidate(callback) import { Tracker } from 'meteor/tracker' Source Registers a new onInvalidate callback on the current computation (which must exist), to be called immediately when the current computation is invalidated or stopped. Arguments callback Function A callback function that will be invoked as func(c), where c is the computation on which the callback is registered.