re-export closure's COMPILED global

dibenede · dibenede · commit b4da468e2bb6 · 2022-10-04T21:30:29.000-07:00
Despite the comments, we do in fact rely on closure's COMPILED global
in CommonJS tests. This variable signals some tests to skip checking
data that has likely been optimized away and is used by things like
debug_test.js that do name checking.

Previously, this was exported by the (now dead) closure testing
asserts export for CommonJS. It has now been re-homed to the testdeps.
diff --git a/commonjs/export_testdeps.js b/commonjs/export_testdeps.js
@@ -13,3 +13,9 @@ goog.require('goog.crypt.base64');
 goog.require('goog.testing.PropertyReplacer');
 
 exports.goog = goog;
+
+// The COMPILED variable is set by Closure compiler to "true" when it compiles
+// JavaScript, so in practice this is equivalent to "exports.COMPILED = true".
+// This will disable some debugging functionality in debug.js, such as
+// attempting to check names that have been optimized away.
+exports.COMPILED = COMPILED
diff --git a/commonjs/rewrite_tests_for_commonjs.js b/commonjs/rewrite_tests_for_commonjs.js
@@ -66,6 +66,7 @@ var pkg = null;
 console.log("var global = Function('return this')();");
 console.log("var googleProtobuf = require('google-protobuf');");
 console.log("var testdeps = require('testdeps_commonjs');");
+console.log("global.COMPILED = testdeps.COMPILED;");
 console.log("global.goog = testdeps.goog;");
 console.log("global.jspb = googleProtobuf;");
 console.log("");
