For Windows, you can [kill meteor like this][1]:

    taskkill /f /im mongod.exe
    taskkill /f /im node.exe

[1]: https://github.com/meteor/windows-preview/issues/30

When I restart Meteor in linux cent-os, I get the following console error:

> Can't listen on port 3000. Perhaps another Meteor is running?
>
> Running two copies of Meteor in the same application directory will not work. If something else is using port 3000, you can specify an alternative port with --port *&lt;port&gt;*.


How can I solve the `--port` error in meteor js

Here's an overview of **`{{#if}}` statements** in Spacebars

### Property

Of course the simplest possible implementation is when the scoped object has a property that evaluates to a boolean

For example if you had:



    var item = {
      text: 'hello',
      checked: false
    };

Then you could evaluate an if block like this:



    class="{{#if checked}}checked{{/if}}"

### Function

We could also evaluate a function here as well.  Rather than add a function to the item, we can add a function to the helper and it will inherit the datacontext of the item being passed to it.  So if we had the following helper:



    Template.item.helpers({
        saysHi: function() {
          return this.text === "hi";
        }
    });

Then we could run the following code:



    <template name="item">
       {{text}}
       {{#if saysHi}} - Hi Back {{/if}}
    </template>

> [**Note**][1]: The helper's implementation can access the current data context as `this`.


### Function with Parameters

You can also pass any number of parameters to helper functions like this:

Template: `{{frob a b c verily=true}}`  
Helper Call: `frob(a, b, c, Spacebars.kw({verily: true}))`

When applied to our if block, we can do the following:



    {{#if equals owner currentUser._id}}
        <button class="delete">&times;</button>
    {{/if}}

Then add `equals` to our template helper like this:



    Template.item.helpers({
        equals: function(v1, v2) {
            return (v1 === v2);
        }
    });

### Universal Helpers

Since this is a generic method that could be useful anywhere, we should add it to every template instead of recreating it.

> [**Note**][2]: To create a helper that can be used in any template, use `Template.registerHelper`.



    Template.registerHelper('equals',
        function(v1, v2) {
            return (v1 === v2);
        }
    );

### [Here's a working Demo in MeteorPad that includes one of each of the types of IF's constructed here][3]

[1]: https://github.com/meteor/meteor/blob/devel/packages/spacebars/README.md#helper-arguments
[2]: http://docs.meteor.com/#/full/template_helpers
[3]: http://meteorpad.com/pad/kntyBuiyBSyDDfAFZ

I am trying to do what I think should be a very simple task, but have been failing to do so in the past hour. I want to select a select option by default if the user property matches the value.

    <select name="myName">
      {{#each addKeys myTable}} 
        <option value="{{key}}" {{#if currentUser.property === key}}selected="selected"{{/if}}>{{value}}</option>
      {{/each}}
    </select>

Now I thought this was straightforward enough to be implemented. But it turns out that Spacebars do not allow conditional operators other than the negation exclamation mark, so equal signs are out of question. I then tried something horrible for the sake of trying:

In template `myTemplate`:

    <select name="myName">
      {{#each addKeys myTable}}
        <option value="{{key}}" {{isSelected currentUser.property key}}>{{value}}</option>
      {{/each}}
    </select>

In `mytemplate.js` :

    Template.myTemplate.helpers({
      isSelected: function(v1, v2) {
        if (v1 === v2)
          return "selected=\"selected\"";
        return '';
      }
    });

Not only is this code terrible, terrible to look at, it does not work:

    Exception in Meteor UI: String contains an invalid character

I don't understand why something that simple seems so impossible to achieve. Am I missing something there?

Check for equality in Spacebars?

You can now use the package **copleykj:livestamp**. ([github][1] | [atmosphere][2])

Install it like this:

    meteor add copleykj:livestamp

It has a dependency on momentjs:moment so it will bring that along automatically.  It installs a universal helper that is available anywhere and can be passed a date object.  

You can use it in a template like this:

    <li>Regular:   {{date}}          </li>
    <li>Livestamp: {{livestamp date}}</li>

### [Here's a working demo in MeteorPad][3]

[1]: https://github.com/copleykj/meteor-livestamp/
[2]: https://atmospherejs.com/copleykj/livestamp
[3]: http://meteorpad.com/pad/JRSxXtnszCqbbyb7K/Livestamp

Have been using https://github.com/acreeger/meteor-moment in meteor and it works well, however is there a way to make the output of moment reactive so that it counts up "3 seconds ago", "4 seconds ago", etc?

Momentjs in meteor- reactivity?

When you install Meteor, it **does not** automatically install node && npm. When installing Meteor, it will download something called `dev_bundle` which has NodeJS and all the NPM modules needed by Meteor. All these modules are pre-compiled for your platform but are not "installed" per-se.

Check out this post if you want to use the node distribubtion included with Meteor: https://meteorhacks.com/how-meteor-uses-node. I suggest you just install Node on your own, though.

I've [installed meteor][1] on my machine:

    curl https://install.meteor.com/ | sh

My understanding is that it meteor runs off of [node.js][2] and automatically installs it.  And node automatically installs [npm][3].

I'm working through the [Discover Meteor tutorial][4] and it has me run:

    npm install -g mup

But I get the following output:

    -bash: npm: command not found

Do I need to run it from a different directory? Or download / install something extra onto my machine.  Add it to my PATH?

[1]: https://www.meteor.com/install
[2]: https://nodejs.org/
[3]: https://www.npmjs.com/
[4]: https://book.discovermeteor.com/chapter/deploying#initializing-meteor-up

I've installed meteor - where is npm?

[`localhost`][1] is a magic string that should do a local DNS lookup which routes to an IPv4 address of `127.0.0.1` or an IPv6 address of `::1`

If you look at your `hosts` file in `C:\Windows\System32\drivers\etc` you should see the following:



    127.0.0.1    localhost
    ::1          localhost

If you're having trouble with the string in some browser (perhaps because of IP address versioning) you can always type in the IP address directly without needing to go through the DNS entry to get there.

So instead of:

http://localhost:3000/

Try using:

http://127.0.0.1:3000/


[1]: https://en.wikipedia.org/wiki/Localhost

I'm reading David Turnbull's fantastic Your First Meteor Application. In his book, he uses the JavaScript console in Chrome to explain points, and I'd love to follow along.  However, when I try and run http://localhost:3000/ I get the following error:

> ERR_CONNECTION_REFUSED

It works perfectly in Firefox and Safari. I'm using a Mac with OS X Yosemite.

I've googled, but nothing suggested on internet works.

Chrome: http://localhost:3000/ - ERR_CONNECTION_REFUSED

Unless there is a meteor-specific way to do this, you can implement the solution from [How to Unit Test Private Functions in JavaScript][1]

You will need to have a single global variable (something like `TestAPI`).  Then add your functions to it inside of a closure so you can access them from anywhere.

Here's an example from the article:



<pre><code>var myModule = (function() {

  function foo() {
    // private function `foo` inside closure
    return "foo"
  }

  var api = {
    bar: function() {
      // public function `bar` returned from closure
      return "bar"
    }
  }

  <b>/* test-code */</b>
  <b>api._foo = foo</b>
  <b>/* end-test-code */</b>

  return api
}())</code></pre>

Someone might have something better, but that's a start.

[1]: http://philipwalton.com/articles/how-to-unit-test-private-functions-in-javascript/

In my server side file I have two functions defined for which I want to write test cases which are residing in a file in tests directory. 

~PRJ_DIR/server/file1.coffee

    
    calcSha1Hash = (params) ->
        .... logic...
    anotherFunc = () ->
        ..somelogic..
        x = calcSha1Hash(params)


~PRJ_DIR/tests/server/file1.coffee

    MochaWeb?.testOnly () ->
      describe.only("Hash generation.  ", () ->
        it(" calcSha1Hash returns Hash.", (dn) ->
          dataDict = {email: 'johndoe@gmail.com'}
          hash = calcSha1Hash (dataDict)
          chai.assert.isDefined(hash)
          dn()
        )
      )

How is it possible to call the server side func(calcSha1Hash) in my test case in Meteor

How to test a server side function in Meteor without including it in global namespace

They are two different sides of the same coin.  Here's a drawing of the data lifecycle in meteor:

![Meteor Data Lifecycle][1]

* [**Publish**][2] - Which data is sent from the *server*  
* [**Subscribe**][3] -  Which data the *client* requests publications for
* [**Methods**][4] - How to manipulate data from the client on the server
 * **Note** - this will typically be run on both on the client and the server.  The client will make a prediction as to what the server will do so it can update right away.  Then *latency compensation* will kick in when the method is run on the server and the canonical decision is made.




[1]: http://i.stack.imgur.com/qoaCi.png
[2]: http://docs.meteor.com/#/full/meteor_publish
[3]: http://docs.meteor.com/#/full/meteor_subscribe
[4]: http://docs.meteor.com/#/full/meteor_methods

What is the difference between **PubSub** and **Methods** in Meteor?!

Can I put Methods in Server folder like Publishs?

To me seen like the same, but Methods is more reactive.


Difference between PubSub and Methods

Yes, it's possible right [out of the box][m1]:

[![enter image description here][1]][2]

Just [initialize the plugin][m2] like this:

    // Initialize collapse button
    $(".button-collapse").sideNav();

### [Demo in Plunker][3]

### Demo in Stack Snippets





    $(".button-collapse").sideNav();



    <link rel="stylesheet" href="//cdnjs.cloudflare.com/ajax/libs/materialize/0.97.0/css/materialize.css">
    <script src="//cdnjs.cloudflare.com/ajax/libs/jquery/2.1.4/jquery.js"></script>
    <script src="//cdnjs.cloudflare.com/ajax/libs/materialize/0.97.0/js/materialize.js"></script>

    <nav>
      <ul class="right hide-on-med-and-down">
        <li><a href="#!">First Sidebar Link</a></li>
        <li><a href="#!">Second Sidebar Link</a></li>
      </ul>
      <ul id="slide-out" class="side-nav">
        <li><a href="#!">First Sidebar Link</a></li>
        <li><a href="#!">Second Sidebar Link</a></li>
      </ul>
      <a href="#" data-activates="slide-out" class="button-collapse"><i class="mdi-navigation-menu"></i></a>
    </nav>



For testing, just enable emulation in the chrome developer tools, reload the page, and swipe in from the edge.




[1]: http://i.stack.imgur.com/7dOGa.gif
[2]: http://i.stack.imgur.com/t8c6q.gif
[3]: http://plnkr.co/edit/ERtNi8yru4DfojXErCsx?p=preview
[m1]: http://materializecss.com/mobile.html
[m2]: http://materializecss.com/side-nav.html#options

I know [Materialize.css][1] has an option to swipe left to dismiss the open sidemenu, but is it possible to open the menu by swiping right as found in most android phones. 

I have a meteor.js implementation for a android app and would want to know if such a feature offered out of the box. 


[1]: http://materializecss.com/

Materialize.css Swipe right to open menu

Here's a complete answer that actually showcases the  reactivity across multiple computers.

### [Working Demo in MeteorPad](http://meteorpad.com/pad/vB5u4koew4GGKzxKe/Secrets)

**lib/collections.js**



    Secrets = new Mongo.Collection("secrets");

**client/templates.js**



    Template.body.helpers({
      secret: function () {
        return Secrets.findOne({}, { sort: { date: -1} });
      }
    });

    Template.body.events({
      'submit form': function (e) {
        // prevent page action
        e.preventDefault();
        
        // get value
        var message = event.target.mySecret.value;
        
        // insert into database
        Secrets.insert({
          text: message,
          date: new Date()
        });
        
        // clear form
        event.target.mySecret.value = "";
      }
    });

**main.html**



    <body>
      {{secret.text}}

      <form>
        <input type="text" name="mySecret" placeholder="Say Something..." />
        <input type="submit" value="Post It"/>
      </form>

    </body>

secrets.meteor.com is a simple application in which each user types in something and when submitted the message is sent in real time through the application for everyone to see, which then is deleted for the next message to show up. 

What is actually being done to make this possible? I'm sorry for the dumb question, but I've searched far an wide on how this is made and have seen nothing. Is each message a function being passed through then executed and deleted?

> **Warning** secrets.meteor.com not sanitze use input!! If you type <code>&lt;script&gt;alert('hi')&lt;/script&gt;</code>, you see an alert, which means anyone can run javascript on your machine. If you really want to check out the site, you're probably okay to open it in an incognito window.

What is used in something like secrets.meteor?

Certainly!  As Kassym noted, `Router.routes` contains a list of all the routes.  However it contains the router *functions*, so you'll have to go and grab their names with [<code>route.<b>getName()</b></code>][1].  The default route doesn't have a name, so you'll have to grab the `.path()` instead.

The whole thing should look like this in your helper:



    Template.allRoutes.helpers({
      paths: function () {
        var allRoutes = _.map(Router.routes, function(route){
          var routeName = typeof route.getName() === 'undefined' ?
                          route.path() :
                          route.getName(); 
          return {route: routeName}
        });
        return allRoutes
      }
    });

And this in your template:



    <template name="allRoutes">
      {{#each paths}}
        <li><a href="{{pathFor route}}">{{route}}</a></li>
      {{/each}}
    </template>

### [Working Demo in MeteorPad][2]



> **Note**: Remember to enclose `pathFor` in curly brackets because it is a helper method.  It will execute javascript and inherit the current datacontext, so you can pass it any property from the current context.

In order to display an sub paths of *n* depth, you can recursively call your template like this:



    <template name="subpaths">
      <ul>
      {{#each subpaths}}
        <li>
          <a href="{{pathFor path}}">{{path}}</a>
          {{#if subpaths}} {{>subpaths}} {{/if}}
        </li>
      {{/each}}
      </ul>
    </template>

[Demo in meteor pad](http://meteorpad.com/pad/EfkKzDhKzKH4GG7R5/All_Routes_Nesting)

For more info, see [getting the names of all routes for the accounts-entry package][3]

[1]: https://github.com/iron-meteor/iron-router#route-names
[2]: http://meteorpad.com/pad/ojj9u6M5DhfCo975v/All_Routes
[3]: https://stackoverflow.com/q/28651428/1366033

Is there a way to add a site map dynamically for all paths which are defined in the Iron Router Router?

I'm thinking of something like this:

    <ul>
	    {{#each paths}}
		    <li><a href="pathFor {{route}}">{{route}}</a></li>
	    {{/each}}
    </ul>

Also, maybe corresponding sub-paths which will be displayed in a child `ul`? 

Obviously I could also just create the list manually, but for an app with 50+ links this is quite of a work.

Find all routes defined in Iron Router

> Uncaught TypeError: $(...).select2 is not a function

The error above happening because you haven't included the JavaScript for Select2, as identified in the comments.  The atmosphere [package you linked to][1] is just for providing Bootstrap-esque styling *on top of* the existing Select2 package.

You should also include [`meteor add natestrauser:select2`][2]

The next problem you may run into is that when the JavaScript runs, `<select class="input" >` might not be loaded into the DOM so `$("#clientName")` won't find anything.  To wait to initialize Select2 until the page is loaded, you should wrap the code in the jQuery's DOM ready function `$(function(){});` and wrap that in the `Meteor.Startup()` for good measure like this:



    Meteor.startup(function () {
      $(function(){
        $("#clientName").select2();
      });
    });

### [Working Demo in Meteorpad][3]

**Further Reading**:

* [How to run JQuery code when document is ready in Meteor?][4]

[1]: https://atmospherejs.com/zimme/select2-bootstrap3-css
[2]: https://atmospherejs.com/natestrauser/select2
[3]: http://meteorpad.com/pad/pHc7QwybBz6wXBRsg/Select2
[4]: https://forums.meteor.com/t/3121

can someone explain to me how select2 works with Meteor? I am using [zimme:select2-boostrap3-css](https://atmospherejs.com/zimme/select2-bootstrap3-css) and I have no clue on how to use it.

I checked both the original [select2 github page](http://select2.github.io/select2/) and the one from the [package](https://github.com/t0m/select2-bootstrap-css/tree/bootstrap3). The first one explains how to use it without Meteor.

Do I just add the jQuery code to one of my *.js-files in order to get it to work?

In HTML:

    <select class="input" id="clientName" name="clientName">
        {{#each getClients}}
            <option value="{{clientName}}" data-id={{_id}}>{{clientName}}</option>
        {{/each}}
    </select>

In JS:
    
    $("#clientName").select2();

Because this doesn't work.

When loading my page I get this error `Uncaught TypeError: $(...).select2 is not a function`.