Different cache folder for different envs

[fasterthanlime]

This issue applies both to electron-compile and electron-compilers, sorry

Reading through a bunch of code right now to find out if a different $TEMP/compileCache_${hash} will get generated if NODE_ENV changes, and.. it doesn't like it does?

Here's the default cache directory code:

export function calculateDefaultCompileCacheDirectory() {
  let tmpDir = process.env.TEMP || process.env.TMPDIR || '/tmp';
  let hash = require('crypto').createHash('md5').update(process.execPath).digest('hex');

  let cacheDir = path.join(tmpDir, `compileCache_${hash}`);
  mkdirp.sync(cacheDir);

  d(`Using default cache directory: ${cacheDir}`);
  return cacheDir;
}

The problem is:

• One might want to enable code coverage (or other babel plugins) only in testing
• But since all files are cached by their content
• And the files wouldn't change, only the compiler settings would
• Then electron-compile would just happily serve the old cached versions (which may have coverage instrumentation when they shouldn't, and the other way around).

You can probably reproduce the problem easily if you use electron-compile with a .babelrc like:

{
  "env": {
    "production": {
      "presets": ["es2016-node5", "react"],
      "sourceMaps": false
    },
    "development": {
      "presets": ["es2016-node5", "react"],
      "sourceMaps": "inline"
    }
  }
}

run it once with NODE_ENV=production, then again with NODE_ENV=development, I'm 80% confident you'd end up not seeing sourceMaps still.

---

Here's my proposal for electron-compile:

• Change calculateDefaultCompileCacheDirectory to feed off of
  • process.execPath
  • process.env.NODE_ENV || "development"
  • the digest for the info/config/opts object (using digest-for-object)
  • see fasterthanlime/electron-compile@a072baf

Tangentially, here's what I've got planned for electron-compilers:

• Add way for compilers to get an input sourceMap
  • compilerContext seems okay
• Make babel compiler consume that input sourceMap when it's there
  • see fasterthanlime@a98839a
• Drop sorcery dependency
  • see fasterthanlime@a98839a
• Make both coverage options (typescript & babel) only apply when NODE_ENV=test
  • Alternatively: only do env matching when coverage is a string, and coverage: true would always instrument, so that the old behavior is retained?
  • Alternatively: don't change anything about the coverage option, force folks to use env blocks
  • see fasterthanlime@a98839a
• Make both coverage option use babel-plugin-istanbul (a relatively thin wrapper over new-istanbul's instrumenting lib).
  • For babel, this means pushing adding a plug-in to the plugins list
  • For typescript, this.. requires babel :/
  • see fasterthanlime@a98839a
• Drop dependency to istanbul 0.4.5 (legacy istanbul) - it's somehow still in electron-compile's package.json
  • see fasterthanlime/electron-compile@e7c2dde
• Document how to set up typescript+babel (babel block in the typescript config)
  • see fasterthanlime/electron-compile@1f7a795
• Document how to set up coverage instrumentation
  • see fasterthanlime/electron-compile@1f7a795
• Document what coverage instrumentation does (collects coverage info using the new istanbul, aka istanbuljs/istanbuljs, into the global __coverage__ variable)
  • see fasterthanlime/electron-compile@1f7a795
• Give an example of collecting/reporting from a __coverage__ variable, with proper sourceMap support (it's like 8 lines).
  • see fasterthanlime/electron-compile@1f7a795

Let me know if any of that sounds bad @paulcbetts & others so I can adjust plans accordingly!

[fasterthanlime]

Additional notes on istanbul@0.4.5 being deprecated: it only became clear to me after spending a day investigating, but: the acorn-based istanbul is pretty dead.

The new istanbul is heavily marketed as nyc (its command-line interface), it's pretty much everything https://istanbul.js.org/ talks about - but there's actual libs underneath, conveniently stashed in this monorepo.

The new instrumenter is based on babel, which makes a bunch of sense:

• If you're already using babel, then the cost of istanbul-lib-instrument is next to non-existent
• If you're not, well.. at least it's more reliable than acorn was.

Quick size comparison:

Legacy istanbul

istanbul-only ツ npm i --save istanbul

+ istanbul@0.4.5
added 60 packages in 5.097s
 istanbul-only ツ du -ch node_modules | tail -1
9.4M    total

babel-plugin-istanbul

babel-plugin ツ npm i --save babel-plugin-istanbul

+ babel-plugin-istanbul@4.1.4
added 107 packages in 8.772s
 babel-plugin ツ du -ch node_modules | tail -1
18M     total

N.B: size of the instrument+coverage+babel plug-in only:

babel-plugin ツ du -ch node_modules/istanbul-lib-* node_modules/babel-plugin-istanbul | tail -1
164K    total

---

TL;DR istanbul is now babel-based, it kinda blows if you're not already using babel, but I don't think electron-compile{,rs} should keep using istanbul@0.4.5

[fasterthanlime]

All done in:

• typescript+babel and coverage improvements #77
• Env-friendly default cache dir + drop legacy istanbul electron-compile#247

Works great for me (typescript+babel, inline source maps):

[fasterthanlime]

Closing in favor of both PRs.