de-globalize console.js constants
progress: remove duplicate assignment
console: avoid division by zero
Revert "console: avoid division by zero"

This reverts commit 2d83bad8f324bd25b884ee1cc2a3fd4924908072.

Whoops, that's not how division by zero works in JS! The existing
isFinite check is fine.
Check for the downloaded tarball plugin matching the requested name

Hackily parse XML with a regex (omg, never do this again) and check the plugin
id declared with id requested.

Should fix #2862.
console: missing vars
console: use utils.sleepMs
document unicode characters
Use util.format for Console print functions

Should be basically backwards compatible (they both join on spaces) but
has the following advantages:

- Objects are printed with util.inspect rather than toString, which
  means no more [object Object].  (We shouldn't be passing objects to
  end-user messages, but they can be useful in Console.debug.)

- The first string can optionally be a printf-style format string, if
  that's a better fit for your message.
use bindEnvironment in forkJoin
add XXX comment about downloading package message
disaster
perhaps this comment is less useful now
replicated
Don't refresh the package cache on the first run

Part of #3006.
catalog.complete should only have one PackageCache

Part of #3006.
Cache files.inCheckout
Merge pull request #3032 from meteor/little-package-cache-fixes

Little package cache fixes
Strip esprima/test from js-analyze
Ensure that Npm.strip is applied in all cases

An Isopack object can be created in one of two ways: by parsing a built
isopack from disk, or by compiling a PackageSource (which may or may not
get written to disk).

In the former case, its nodeModulesPath field will be something like
"npm/node_modules", referring to the node_modules directory inside the
built isopack, which has already had Npm.strip applied to it.

In the latter case, its nodeModulesPath field is actually the
pre-stripped node modules directory (eg '.npm/package/node_modules'). So
if we were to use such an Isopack object inside a bundler operation, we
would need to actually apply the strip operation at bundle time.

As far as I can tell it may not actually be possible to trigger this bug
yet, because for some reason we never quite seem to use the built
Isopack in bundler without cycling it through disk. But I've managed to
trigger it on the isopackets branch, and it's certainly a goal to use
our in-memory caches better (and not require unnecessary write/read
cycles).