Try adding output blocks and configure evaldown to capture the console

README.md

@@ -62,6 +62,10 @@ const renderer = counteraction('lower-roman');
 console.log(renderer.render(123)); // cxxiii
 ```
 
+```output
+cxxiii
+```
+
 The `@counter-system` ones are created by their `system` name and accept an
 options object that corresponds to the CSS properties of the `@counter-style`
 declaration:
@@ -73,6 +77,10 @@ const renderer = counteraction('alphabetic', {
 console.log(renderer.render(123)); // XXXXZ
 ```
 
+```output
+cxxiii
+```
+
 The name (system) can also be passed as a separate property instead of the name
 parameter. That might be easier if you're working with a parsed representation
 of the whole `@counter-style` declaration:
@@ -85,6 +93,10 @@ const renderer = counteraction({
 console.log(renderer.render(123)); // XXXXZ
 ```
 
+```output
+XXXXZ
+```
+
 They also support a `fallback` option to be used when the value is out of range.
 It can be passed as either a renderer instance or the name of a
 `list-style-type` renderer:
@@ -98,4 +110,9 @@ console.log(renderer.render(3)); // Z
 console.log(renderer.render(4)); // •
 ```
 
+```output
+Z
+•
+```
+
 The `fallback` option can also be passed as another renderer instance, or "lazily" as a function that returns either a `list-style-type` name or a renderer.

package.json

@@ -27,7 +27,7 @@
   "scripts": {
     "lint": "eslint . && prettier --check '**/*.js'",
     "test": "mocha",
-    "test:documentation": "evaldown README.md >/dev/null",
+    "test:documentation": "evaldown --output-capture=console README.md >/dev/null",
     "test:ci": "npm run coverage && npm run test:documentation",
     "coverage": "NODE_ENV=development nyc --reporter=lcov --reporter=text --all -- npm test && echo google-chrome coverage/lcov-report/index.html"
   },