82f2b76e25
We now use webpack instead of SystemJS, effectively bundling modules into one file (plus commons chunks) for every entry point. This results in a much smaller extension size (almost half). Furthermore we use yarn/npm even for extension run-time dependencies. This relieves us from manually vendoring and building dependencies. It's also easier to understand for new developers familiar with node. |
||
|---|---|---|
| .. | ||
| dist | ||
| node_modules/.bin | ||
| CHANGELOG.md | ||
| LICENSE | ||
| package.json | ||
| README.md | ||
istanbul-lib-instrument
Istanbul instrumenter library.
Version 1.1.x now implements instrumentation using Babel. The implementation is inspired
by prior art by @dtinth as demonstrated in the __coverage__ babel plugin.
It provides 2 "modes" of instrumentation.
-
The old API that is mostly unchanged (except for incompatibilities noted) and performs the instrumentation using babel as a library.
-
A
programVisitorfunction for the Babel AST that can be used by a Babel plugin to emit instrumentation for ES6 code directly without any source map processing. This is the preferred path for babel users. The Babel plugin is calledbabel-plugin-istanbul.
Incompatibilities and changes to instrumentation behavior can be found in v0-changes.md.