You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/recipes/code-coverage.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -64,9 +64,9 @@ First, we need a Babel configuration. The following is just an example. You will
64
64
65
65
There are two important things to note from the example above.
66
66
67
-
1. We ignore test files because AVA already handles transpiling tests for you.
67
+
1. We ignore test files because AVA already handles transpiling tests for you.
68
68
69
-
2. We specify `inline` source maps for development. This is important for properly generating coverage. Using the `env` section of the Babel configuration allows us to disable source maps for production builds.
69
+
2. We specify `inline` source maps for development. This is important for properly generating coverage. Using the `env` section of the Babel configuration allows us to disable source maps for production builds.
70
70
71
71
72
72
### Create a build script
@@ -77,15 +77,15 @@ Since it is unlikely you want `inline` source maps in your production code. You
> WARNING: `BABEL_ENV=production` does not work on Windows, you must use the `set` keyword (`set BABEL_ENV=production`). For cross platform builds, check out [`cross-env`].
87
87
88
-
Note that the build script really has very little to do with AVA, and is just a demonstration of how to use Babel's `env` configuration to manipulate your config so it is compatible with AVA.
88
+
Note that the build script really has very little to do with AVA, and is just a demonstration of how to use Babel's `env` configuration to manipulate your config so it's compatible with AVA.
89
89
90
90
### Use the Babel require hook
91
91
@@ -167,7 +167,7 @@ Then add the following to your `.travis.yml`:
Copy file name to clipboardExpand all lines: docs/recipes/endpoint-testing.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,7 @@ function makeApp() {
14
14
}
15
15
```
16
16
17
-
Next, just inject your server instance into supertest. The only gotcha is to use a promise or async/await syntax instead of supertest's`end` method:
17
+
Next, just inject your server instance into supertest. The only gotcha is to use a promise or async/await syntax instead of the supertest `end` method:
0 commit comments