mirror of
https://github.com/react/react-native-devtools-frontend.git
synced 2026-09-29 16:57:00 +08:00
Tim van der Lippe
fe1b426acc
- Update istanbul-lib-instrument (breaking change is not affecting us) - Explicitly update @istanbuljs/schema to 0.1.3. This directly instructs Babel to accept top-level await. As such, we can remove our special configuration for our `ui/components/docs` folder, which we can now safely preprocess. DISABLE_THIRD_PARTY_CHECK=Karma fix R=jacktfranklin@chromium.org Bug: none Change-Id: I0e96dce0117550f1a2db6a93654d8862d9cae95a Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/3158226 Commit-Queue: Tim van der Lippe <tvanderlippe@chromium.org> Commit-Queue: Jack Franklin <jacktfranklin@chromium.org> Auto-Submit: Tim van der Lippe <tvanderlippe@chromium.org> Reviewed-by: Jack Franklin <jacktfranklin@chromium.org>
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.