v8-to-istanbul
npmv9.3.0TypeScriptconvert from v8 coverage format to istanbul's format
Adopt with care
v8-to-istanbul is usable, with caveats. Last published 809 days ago.
- ?Adoption: grade ?, Not reported by this registry.
No download data reported for this package yet.
- DMaintenance: grade D, Poor — a real concern.
Last published 809 days ago.
- AWeight: grade A, Excellent.
Pulls in 5 transitive packages, about 357 KB installed.
- ASupply chain: grade A, Excellent.
No install scripts, 2 maintainers, and a contained dependency surface.
- ALicense: grade A, Excellent.
ISC — permissive, with no copyleft found in the dependency tree.
Grades are computed deterministically from registry metadata collected by PackageGraph — downloads, dependents, publish dates, the resolved dependency tree, maintainer count, and declared licenses. No third-party scores are used.
Install cost
What you actually take on by adding v8-to-istanbul to a project.
Runtime packages this one declares itself.
Distinct packages in the full runtime tree, deduplicated the way a package manager would.
Unpacked size of this package plus its entire runtime tree.
Longest resolved dependency chain below this package.
Licenses in the dependency tree
Every license you inherit by installing v8-to-istanbul, not just its own. Check this before a legal review, not after.
Compatibility
- Node.js
- node >=10.12.0
- Module format
- CommonJS only
- TypeScript
- Types included
- Install scripts
- None
Quick start
A usage example from the v8-to-istanbul README.
const v8toIstanbul = require('v8-to-istanbul')
// the path to the original source-file is required, as its contents are
// used during the conversion algorithm.
const converter = v8toIstanbul('./path-to-instrumented-file.js')
await converter.load() // this is required due to async file reading.
// provide an array of coverage information in v8 format.
converter.applyCoverage([
{
"functionName": "",
"ranges": [
{
"startOffset": 0,
"endOffset": 520,
"count": 1v8-to-istanbul vs the alternatives
Packages solving a similar problem in the npm ecosystem, compared on the signals that drive an adoption decision.
| Package | Weekly downloads | Dependents | License | Last release |
|---|---|---|---|---|
| v8-to-istanbulthis page | 0 | 1 | ISC | 2 years ago |
| @vitest/istanbul-lib-coverage | 495.5K | 7 | MIT | 1 day ago |
| @vitest/istanbul-lib-instrument | 24.9K | 2 | MIT | 1 day ago |
| @vitest/coverage-istanbul | 0 | 4 | MIT | 1 day ago |
| istanbul-lib-coverage | 0 | 10 | BSD-3-Clause | 1 day ago |
| istanbul-lib-instrument | 0 | 4 | BSD-3-Clause | 1 day ago |
Dependencies
Declared by v8-to-istanbul v9.3.0. Runtime dependencies are installed with the package; dev dependencies are not.
Runtime (3)
Dev (7)
Used by
Popular packages that depend on v8-to-istanbul.
Relationship graph
Dependencies (left) and dependents (right) of v8-to-istanbul.
Frequently installed together
A Node.js module for sending notifications on native Mac, Windows (post and pre 8) and Linux (or Growl as fallback)
This packages is a collection of utilities and helper functions
No description provided.
Source maps support for istanbul
No description provided.
`@jest/pattern` is a helper library for the jest library that implements the logic for parsing and matching patterns.
No description provided.
Module for executing heavy tasks under forked processes in parallel, by providing a `Promise` based interface, minimum overhead, and bound workers.
Convert Windows backslash paths to slash paths
Trace the original position through a source map
TypeScript definitions for istanbul-reports
TypeScript definitions for istanbul-lib-coverage
Release history
No releases in the last two years, typically about 48 days apart.
| Version | Published | Size | License |
|---|---|---|---|
| 9.3.0latest | 2 years ago | 47 KB | ISC |
| 9.2.0 | 2 years ago | 46 KB | ISC |
| 9.1.3 | 2 years ago | 45 KB | ISC |
| 9.1.2 | 2 years ago | 45 KB | ISC |
| 9.1.1 | 2 years ago | 44 KB | ISC |
| 9.1.0 | 3 years ago | 44 KB | ISC |
| 9.0.1 | 4 years ago | 44 KB | ISC |
| 9.0.0 | 4 years ago | 43 KB | ISC |
| 8.1.1 | 4 years ago | 43 KB | ISC |
| 8.2.0-candidate.1 | 4 years ago | 27 KB | ISC |
| 9.0.0-candidate.0 | 4 years ago | 28 KB | ISC |
| 8.1.0 | 5 years ago | 41 KB | ISC |
| 8.0.0 | 5 years ago | 40 KB | ISC |
| 7.1.2 | 5 years ago | 40 KB | ISC |
| 7.1.1 | 5 years ago | 39 KB | ISC |
Overview
v8-to-istanbul is an npm package that convert from v8 coverage format to istanbul's format. It has 1 known dependents in the graph. The latest version is 9.3.0, released under the ISC license.
Who should use it
Teams working in the npm ecosystem who need convert from v8 coverage format to istanbul's format and value a focused solution.
When not to use it
Consider an alternative if you need to or if a more actively-maintained option better fits your npm stack.
Pros
- Ships TypeScript type definitions.
- Clear open-source license (ISC).
Cons
- No significant drawbacks detected from available metadata.
Auto-generated from collected registry metadata. No external claims are inferred.
Frequently asked questions
Should I use v8-to-istanbul?
v8-to-istanbul is usable, with caveats. Last published 809 days ago.
How do I install v8-to-istanbul?
Run `npm install v8-to-istanbul` to add v8-to-istanbul to your npm project.
How many dependencies does v8-to-istanbul have?
v8-to-istanbul declares 10 direct dependencies and pulls in 5 packages in total once its runtime tree is resolved totalling about 357 KB on disk.
What license is v8-to-istanbul released under?
v8-to-istanbul is distributed under the ISC license.
How popular is v8-to-istanbul?
npm does not publish download counts. Within PackageGraph's crawl, 1 known packages depend on v8-to-istanbul.
Is v8-to-istanbul still maintained?
The most recent release of v8-to-istanbul (v9.3.0) was published 2 years ago.
Does v8-to-istanbul run install scripts?
No. v8-to-istanbul does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.