bruceharris/README.md

## README.md

      
    Raw
  

              README.md
            
          
    Meteor namespacing, specifically package scope variables, don't seem to work as described in the namespacing section of the docs.
From what I can tell, when the var keyword is omitted, actual globals are created. (I'm running 0.6.5)
To run this:
$ meteor create globalcheck

then copy these files into globalcheck (overwriting the default files)

  
## globalcheck.html
<head>
  <title>globalcheck</title>
</head>

<body>
  {{> hello}}
</body>

<template name="hello">
  {{greeting}}
</template>

## globalcheck.js
foo = "truly global, not package scope";

if (Meteor.isClient) {
  Template.hello.greeting = function () {
    // window.foo is truly global, not package scope
    return "window.foo is " + window.foo;
  };
}

if (Meteor.isServer) {
  Meteor.startup(function () {
    // global.foo is truly global, not package scope
    console.log("global.foo is " + global.foo);
  });
}
	<head>
	<title>globalcheck</title>
	</head>

	<body>
	{{> hello}}
	</body>

	<template name="hello">
	{{greeting}}
	</template>
	foo = "truly global, not package scope";

	if (Meteor.isClient) {
	Template.hello.greeting = function () {
	// window.foo is truly global, not package scope
	return "window.foo is " + window.foo;
	};
	}

	if (Meteor.isServer) {
	Meteor.startup(function () {
	// global.foo is truly global, not package scope
	console.log("global.foo is " + global.foo);
	});
	}