Just a heads up, a few of us have run into problems with extensions breaking in nightly. The problem is probably not restricted to extensions.

The scoping rules for const in JavaScript have changed to conform w/ the ES6 spec [1]. My understanding is that a const variable is now restricted to the scope it was declared in.

Basically the following no longer works:

  if (foo) {
     const bar = ...;
  }

  bar.baz();

This broke lightbeam [2], mozmill 1.5 (I believe it's fixed in the 2.0 branch) which AWSY uses, and probably plenty of other things that have been using const since, I'm not sure when it showed up, but at least the past 4 years.

So if you're seeing failures since around 11/5 this could be it, you just need to rework the scope of your const statements (and maybe not use const unfortunately).

-e

[1] https://bugzilla.mozilla.org/show_bug.cgi?id=611388
[2] https://github.com/mozilla/lightbeam/issues/622
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Reply via email to