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 🙏

© 2024 – Pkg Stats / Ryan Hefner

rollup-plugin-istanbul

v5.0.0

Published

Seamless integration between Rollup and Istanbul.

Downloads

252,721

Readme

rollup-plugin-istanbul

Build Status Maintainability Last version Total Downloads Downloads Last Month License

Seamless integration between Rollup and Istanbul.

Why?

If you're using Rollup to generate a standalone bundle you will probably need also to bundle your tests before running them, and if you want the code coverage report, you will need to instrument the program files before the bundle is generated to avoid instrumenting also the code of the test files.

That is the reason why rollup-plugin-istanbul exists.

Installation

npm install --save-dev rollup-plugin-istanbul
# or
yarn add -D rollup-plugin-istanbul
# or
pnpm add -D rollup-plugin-istanbul

Usage

import { rollup } from 'rollup';
import istanbul from 'rollup-plugin-istanbul';

rollup({
  entry: 'main.js',
  plugins: [
    istanbul({
      exclude: ['test/**/*.js']
    })
  ]
}).then(...)

Options

All options are optional.

include

Can be a minimatch pattern or an array of minimatch patterns. If is omitted or of zero length, files should be included by default; otherwise they should only be included if the ID matches one of the patterns.

exclude

Can be a minimatch pattern or an array of minimatch patterns. Files to exclude, commonly the test files.

instrumenterConfig

An object of options that will be passed to the instrumenter.

Default value:

{
  esModules: true,
  compact: true,
  produceSourceMap: true,
  autoWrap: true,
  preserveComments: true
}

More info about options.

instrumenter

Can be a replacement for the istanbul library, for example isparta. It should implement the same API as istanbul.

Other usage options

rollup-plugin-istanbul can be used with karma or other test runners that allow preprocessors. Here you can see how to implement it with Karma with the help of the karma-rollup-preprocessor and karma-coverage:

// karma.conf.js
var istanbul = require("rollup-plugin-istanbul")

module.exports = function (config) {
	config.set({
		files: ["test/*.js"],
		preprocessors: {
			"test/*.js": ["rollup"],
		},
		rollupPreprocessor: {
			rollup: {
				plugins: [
					istanbul({
						exclude: ["test/*.js"],
					}),
				],
			},
		},
		reporters: ["coverage"],
	})
}

Going further, this is how you can implement it when you are using babel because you are writing ES2015 code:

// karma.conf.js

const istanbul = require("rollup-plugin-istanbul")
const babel = require("@rollup/plugin-babel").babel

module.exports = function (config) {
	config.set({
		files: ["test/*.js"],
		preprocessors: {
			"test/*.js": ["rollup"],
		},
		rollupPreprocessor: {
			plugins: [
				istanbul({
					exclude: ["test/*.js"],
				}),
				babel({ babelHelpers: "bundled" }),
			],
			output: {
				format: "iife",
				sourceMap: "inline",
			},
		},
		reporters: ["coverage"],
		coverageReporter: {
			dir: "coverage",
			includeAllSources: true,
			reporters: [
				{ type: "text" },
				{ type: "html", subdir: "html" },
				{ type: "lcov", subdir: "./" },
			],
		},
	})
}

Example of implementation provided in examples folder.

License

http://opensource.org/licenses/MIT

Copyright (c) 2016-2023 Alberto Varela Sánchez & Contributors

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.