mirror of
https://github.com/meteor/meteor.git
synced 2026-05-02 03:01:46 -04:00
7a18012975
The most fool-proof way to tell if a module is provided by babel-runtime is to load babel-runtime as an isopacket and ask it. This should fix any remaining issues like this one: https://github.com/meteor/meteor/pull/7668#pullrequestreview-4379559
Uninteresting files that run on tool's startup (set up profilers, transpilers, etc) and exit (clean up code, flush the output).
ES2015 compilation for tool
There are two different configurations of Babel for the tools code:
- local development from git checkout
- running in production from a release
In the first case, it is enough to register Babel's hook for require. For the
latter, this hook should be removed (#RemoveInProd) and the files should be
explicitly compiled.
The listing of Babel-compiled files can be found in isopack.js, the
Isopack#_writeTool method runs all the preprocessing when tools files are
copied for a release package.