Whenever I submit a plugin to Firefox I get an email telling me some of my variables are leaking into the global scope... once they tell me I fix the issue. But till then is there any way (program?) to check if the variables are leaking into the global scope?

Thanks!

Whenever I submit a plugin to Firefox I get an email telling me some of my variables are leaking into the global scope... once they tell me I fix the issue. But till then is there any way (program?) to check if the variables are leaking into the global scope?

Thanks!

• javascript
• global-variables

• 1 stackoverflow./questions/6616267/… – nobody Commented Jul 26, 2011 at 17:18
• Different, here am asking for a tool... there i had no idea what was going on... – Ryan Commented Jul 26, 2011 at 18:11
• I didn't notice you're the same person :) – nobody Commented Jul 26, 2011 at 20:56

5 Answers 5

Both JSLint and JSHint will give you warnings when you miss a var. Both are available on Github (JSLint, JSHint) and both can be run from the mand line using Node.js, Rhino or any other non-browser environment of your choice. They can even be integrated into your text editor / IDE of choice and run with a keystroke.

The ECMAScript standard 5th edition introduces an optional "strict mode", which forces you to use a cleaner subset of JS. In strict mode, if you try to assign to a variable that hasn't been declared with the var keyword, a ReferenceError will be thrown.

You can enable strict mode inside a function, or in the entire file, by including this as the first statement:

"use strict";

I'd remend strict mode for your problem. It's already implemented in recent versions of major browsers. See here for an overview:

https://developer.mozilla/en/JavaScript/Strict_mode

The lint tools others have remended are an excellent idea, and will point you at the problem, but if you have unittests, you can incorporate tests for leaked globals into them.

Just run this before you load your source code,

var globalsBeforeLoad = {};
(function () {
  for (var k in this) { globalsBeforeLoad[k] = true; }
})()

and then run this after you load your code

(function () {
  var leaked = [];
  for (var k in this) {
    if (!Object.hasOwnProperty.call(globalsBeforeLoad, k)) {
      leaked.push(k);
    }
  }
  if (leaked.length) { alert("You leaked " + leaked.join(", ")); }
})()

Any variable declaration inside a function that doesn't start with var will leak into global scope. You can check for those.

Declare all your variables at the top of each function.

The worst of all of JavaScript's bad features is its dependence on global variables. A global variable is a variable that is visible in every scope. Global variables can be a convenience in very small programs, but they quickly bee unwieldy as programs get larger. Because a global variable can be changed by any part of the program at any time, they can significantly plicate the behavior of the program. Use of global variables degrades the reliability of the programs that use them. [...] In most languages, it is generally best to declare variables at the site of first use. That turns out to be a bad practice in JavaScript because it does not have block scope. It is better to declare all variables at the top of each function.

"JavaScript: The Good Parts by Douglas Crockford. Copyright 2008 Yahoo! Inc., 978-0-596-51774-8."