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

Server accountsServer.validateLoginAttempt(func) Source Validate login attempts. Arguments func Function Called whenever a login is attempted (either successful or unsuccessful). A login can be aborted by returning a falsy value or throwing an exception.

App.launchScreens(launchScreens) Set the launch screen images for your mobile app. Arguments launchScreens Object A dictionary where keys are different devices, screen sizes, and orientations, and the values are image paths relative to the project root directory. For Android, launch screen images should be special "Nine-patch" image files that specify how they should be stretched. See the Android docs. Valid key values: iphone_2x (640x960) iphone5 (640x1136) iphone6 (750x1334) iphone

Anywhere check(value, pattern) import { check } from 'meteor/check' Source Check that a value matches a pattern. If the value does not match the pattern, throw a Match.Error. Particularly useful to assert that arguments to a function have the right types and structure. Arguments value Any The value to check pattern Match Pattern The pattern to match value against

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

Introduction Testing allows you to ensure your application works the way you think it does, especially as your codebase changes over time. If you have good tests, you can refactor and rewrite code with confidence. Tests are also the most concrete form of documentation of expected behavior, since other developers can figure out how to use your code by reading the tests. Automated testing is critical because it allows you to run a far greater set of tests much more often than you could manually,

Client new Blaze.Template([viewName], renderFunction) import { Blaze } from 'meteor/blaze' Source Constructor for a Template, which is used to construct Views with particular name and content. Arguments viewName String Optional. A name for Views constructed by this Template. See view.name. renderFunction Function A function that returns renderable content. This function is used as the renderFunction for Views constructed by this Template.

Client Blaze.remove(renderedView) import { Blaze } from 'meteor/blaze' Source Removes a rendered View from the DOM, stopping all reactive updates and event listeners on it. Arguments renderedView Blaze.View The return value from Blaze.render or Blaze.renderWithData.

App.configurePlugin(id, config) Set the build-time configuration for a Cordova plugin. Arguments id String The identifier of the plugin you want to configure. config Object A set of key-value pairs which will be passed at build-time to configure the specified plugin.

After reading this guide, you’ll know: The security surface area of a Meteor app. How to secure Meteor Methods, publications, and source code. Where to store secret keys in development and production. How to follow a security checklist when auditing your app. Introduction Securing a web application is all about understanding security domains and understanding the attack surface between these domains. In a Meteor app, things are pretty simple: Code that runs on the server can be trusted. Every