Files
meteor/tools/tool-env
David Greenspan 601cfbcebd Don't re-parse versions during sorting; profiling
- We don't want to do a bunch of parsing *per comparison* when sorting
  a list of package version strings.  package-version-parser's `compare`
  (and server's `compare`, which it uses) both accept either a string
  or a parsed record.  By parsing explicitly with memoization, we avoid
  a super-linear blow-up in the amount of parsing.  This'll save someone
  half a second, at least.
- Adjust profiling hooks and messages
- Expose `Profile` to isopackets
2016-02-05 10:04:31 -08:00
..
2015-08-05 15:03:53 -07:00

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.