Compiled files missing runtime (i.e. $traceurRuntime is not defined)

[chirayuk]

The Bug

According to the Wiki on Compiling Offline, one does not need to include traceur-runtime.js.

If I don't include traceur-runtime.js, I get the console error $traceurRuntime is not defined (the very first line of compiled file is $traceurRuntime.ModuleStore.registerModule(…)) (using master/HEAD)

Original bug

issue 288 was fixed in commit 106c4203915f6bc77d570246761bd61b9ec9aa73

Regression

commit 0575566752ec48f8c36edae0c614c8a55eb31d78 changed the test for running the compiled class (introduced in the earlier bugfix) from executeFile to executeFileWithRuntime.  This now passes because it's including the runtime.

Since this addressed issue 501: Separate the runtime functions into a file built independent of the compiled output, is one always required to include traceur-runtime.js somewhere and the Compiling Offline wiki is just out of date and needs updating?

[arv]

You now need the runtime in almost all cases.

The second change is that the command line compiler now compiles the input as modules by default.

I'll try to clean up the wiki page a little.

[arv]

Updated wiki.

Also note that traceur-runtime.js is fubared #780

[arv]

@johnjbarton

[johnjbarton]

A runtime is always needed.
The procedure outlined in the Compiling Offline Wiki page creates a compiled file without the runtime and then adds the runtime by including bin/traceur-runtime.js.
Alternatively the runtime can be compiled into the compiled file using the same procedure we use for bin/traceur.js: the runtime source files are fed to the compiler before the application files. I guess we could document this, but it has been a moving target recently.

Thanks for the information about the out-of-date Wiki page.

[chirayuk]

Sweet.  Thanks for the information and fixes!