npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

ts-es5-istanbul-coverage

v1.0.6

Published

Make sure you don't miss branch coverage when outputing TypeScript as ES5

Readme

ts-es5-istanbul-coverage

Make sure you don't miss branch coverage when outputing TypeScript as ES5

Goal

When your project uses TypeScript exported as ES5, Webpack for build and Instanbul for the code coverage, you may encounter some impossible to cover branches. This is because of how TypeScript emits files. You can read more on the subject :

  • https://github.com/SitePen/remap-istanbul/issues/106
  • https://github.com/Microsoft/TypeScript/issues/13455
  • https://github.com/gotwarlost/istanbul/issues/690

This little webpack loader will add /* istanbul ignore next */ where needed.

Install

yarn add ts-es5-istanbul-coverage --dev or npm install ts-es5-istanbul-coverage --save-dev

Usage

Simply configure the loader as any other loader. Note: It must run After the actual typescript transpilation (so it should appear first in the webpack configuration rule)

Example of confuguration using ts-loader and ts-es5-istanbul-coverage

module.exports = {
	module: {
		rules: [
			// all files with a `.ts` or `.tsx` extension will be handle
			{
				test: /\.tsx?$/,
				use: [
					{
						loader: 'ts-es5-istanbul-coverage',
					},
					{
						loader: 'ts-loader',
					},
				],
			}
		]
	}
}

Current fixes

Currently the loader fix the branch coverage for the following: Emitted code like:

function MyClass() {
	return _super !== null && _super.apply(this, arguments) || this;
}

will be replaced by

function MyClass() {
	/* istanbul ignore next */return _super !== null && _super.apply(this, arguments) || this;
}

Which solves the coverage for the branch || this

Emitted code like:

function MyClass() {
    return _this;
    var _a, _b;
}

will be replaced by

function MyClass() {
    var _a, _b;
    return _this;
}

Which solves the coverage for the var statement

Emitted code like:

for (var _i = 0; _i < arguments.length; _i++) {
	dependencies[_i] = arguments[_i];
}

will be replaced by

for (var _i = 0; _i < arguments.length; _i++) {/* istanbul ignore next */
	dependencies[_i] = arguments[_i];
}

Which solves the coverage for the loop body