Files
meteor/tools/tests
Ben Newman 41e9ee857e Evaluate dynamic module code in package scope.
This should elegantly address the issues described in this comment:
https://github.com/meteor/meteor/pull/8327#issuecomment-280881830

I toyed with the possibility of turning package variables (both imports
from other packages and intercepted "global" variable assignments) into
properties on a shared namespace object, but that would have been a major
breaking change for existing package code, because it would have required
automatically rewriting variable references in package modules.
2017-02-21 11:47:31 -05:00
..
2016-03-17 21:20:12 +01:00
2016-03-17 16:48:25 +01:00
2016-03-17 16:48:25 +01:00
2016-06-06 02:17:36 +03:00
2016-11-02 12:47:01 -04:00
2015-08-06 16:39:00 -07:00
2016-05-13 15:09:03 -07:00
2016-11-02 14:18:42 -04:00