source: frontend/node_modules/babel-plugin-istanbul/README.md

Last change on this file was 9af201e, checked in by MBK <marija.karapandzova@…>, 12 days ago

Fix frontend appearance

  • Property mode set to 100644
File size: 4.8 KB
RevLine 
[9af201e]1# babel-plugin-istanbul
2
3[![Coverage Status](https://coveralls.io/repos/github/istanbuljs/babel-plugin-istanbul/badge.svg?branch=master)](https://coveralls.io/github/istanbuljs/babel-plugin-istanbul?branch=master)
4[![Conventional Commits](https://img.shields.io/badge/Conventional%20Commits-1.0.0-yellow.svg)](https://conventionalcommits.org)
5[![community slack](http://devtoolscommunity.herokuapp.com/badge.svg)](http://devtoolscommunity.herokuapp.com)
6
7_Having problems? want to contribute? join our [community slack](http://devtoolscommunity.herokuapp.com)_.
8
9A Babel plugin that instruments your code with Istanbul coverage.
10It can instantly be used with [karma-coverage](https://github.com/karma-runner/karma-coverage) and mocha on Node.js (through [nyc](https://github.com/bcoe/nyc)).
11
12__Note:__ This plugin does not generate any report or save any data to any file;
13it only adds instrumenting code to your JavaScript source code.
14To integrate with testing tools, please see the [Integrations](#integrations) section.
15
16## Usage
17
18Install it:
19
20```
21npm install --save-dev babel-plugin-istanbul
22```
23
24Add it to `.babelrc` in test mode:
25
26```js
27{
28 "env": {
29 "test": {
30 "plugins": [ "istanbul" ]
31 }
32 }
33}
34```
35
36Optionally, use [cross-env](https://www.npmjs.com/package/cross-env) to set
37`NODE_ENV=test`:
38
39```json
40{
41 "scripts": {
42 "test": "cross-env NODE_ENV=test nyc --reporter=lcov --reporter=text mocha test/*.js"
43 }
44}
45```
46
47## Integrations
48
49### karma
50
51It _just works_ with Karma. First, make sure that the code is already transpiled by Babel (either using `karma-babel-preprocessor`, `karma-webpack`, or `karma-browserify`). Then, simply set up [karma-coverage](https://github.com/karma-runner/karma-coverage) according to the docs, but __don’t add the `coverage` preprocessor.__ This plugin has already instrumented your code, and Karma should pick it up automatically.
52
53It has been tested with [bemusic/bemuse](https://codecov.io/github/bemusic/bemuse) project, which contains ~2400 statements.
54
55### mocha on node.js (through nyc)
56
57Configure Mocha to transpile JavaScript code using Babel, then you can run your tests with [`nyc`](https://github.com/bcoe/nyc), which will collect all the coverage report.
58
59babel-plugin-istanbul respects the `include`/`exclude` configuration options from nyc,
60but you also need to __configure NYC not to instrument your code__ by adding these settings in your `package.json`:
61
62```js
63 "nyc": {
64 "sourceMap": false,
65 "instrument": false
66 },
67```
68
69## Ignoring files
70
71You don't want to cover your test files as this will skew your coverage results. You can configure this by providing plugin options matching nyc's [`exclude`/`include` rules](https://github.com/bcoe/nyc#excluding-files):
72
73```json
74{
75 "env": {
76 "test": {
77 "plugins": [
78 ["istanbul", {
79 "exclude": [
80 "**/*.spec.js"
81 ]
82 }]
83 ]
84 }
85 }
86}
87```
88
89If you don't provide options in your Babel config, the plugin will look for `exclude`/`include` config under an `"nyc"` key in `package.json`.
90
91You can also use [istanbul's ignore hints](https://github.com/gotwarlost/istanbul/blob/master/ignoring-code-for-coverage.md#ignoring-code-for-coverage-purposes) to specify specific lines of code to skip instrumenting.
92
93## Source Maps
94
95By default, this plugin will pick up inline source maps and attach them to the instrumented code such that code coverage can be remapped back to the original source, even for multi-step build processes. This can be memory intensive. Set `useInlineSourceMaps` to prevent this behavior.
96
97```json
98{
99 "env": {
100 "test": {
101 "plugins": [
102 ["istanbul", {
103 "useInlineSourceMaps": false
104 }]
105 ]
106 }
107 }
108}
109```
110
111If you're instrumenting code programatically, you can pass a source map explicitly.
112```js
113import babelPluginIstanbul from 'babel-plugin-istanbul';
114
115function instrument(sourceCode, sourceMap, fileName) {
116 return babel.transform(sourceCode, {
117 filename,
118 plugins: [
119 [babelPluginIstanbul, {
120 inputSourceMap: sourceMap
121 }]
122 ]
123 })
124}
125```
126
127## Credit where credit is due
128
129The approach used in `babel-plugin-istanbul` was inspired by [Thai Pangsakulyanont](https://github.com/dtinth)'s original library [`babel-plugin-__coverage__`](https://github.com/dtinth/babel-plugin-__coverage__).
130
131## `babel-plugin-istanbul` for enterprise
132
133Available as part of the Tidelift Subscription.
134
135The maintainers of `babel-plugin-istanbul` and thousands of other packages are working with Tidelift to deliver commercial support and maintenance for the open source dependencies you use to build your applications. Save time, reduce risk, and improve code health, while paying the maintainers of the exact dependencies you use. [Learn more.](https://tidelift.com/subscription/pkg/npm-babel-plugin-istanbul?utm_source=npm-babel-plugin-istanbul&utm_medium=referral&utm_campaign=enterprise&utm_term=repo)
Note: See TracBrowser for help on using the repository browser.