Create recipe "Debugging with node inspect"

docs/recipes/debugging-with-node-inspect.md

@@ -0,0 +1,24 @@
+# Debugging tests with node-inspect
+
+Because AVA executes its tests in parallel over multiple worker processes, it doesn't play nice with node's inspect feature by default.
+
+If you want to use the [node inspect CLI debugger](https://nodejs.org/api/debugger.html), you can use the `profile.js` entrypoint like this:
+```
+node inspect ./node_modules/ava/profile.js <file>
+```
+Where `<file>` is the test you want to debug. It is currently only possible to debug one test file at a time.
+
+If you want to use yarn or npm to start the debugger you can add the following script in your `package.json`:
+
+```json
+{
+  "scripts": {
+    "test:debug": "node inspect ./node_modules/ava/profile.js --"
+  }
+}
+```
+
+You can now debug in your console using:
+
+- npm: `npm run test:debug test/test.js`
+- yarn: `yarn run test:debug test/test.js`

readme.md

@@ -170,6 +170,7 @@ We have a growing list of [common pitfalls](docs/08-common-pitfalls.md) you may
 - [Debugging tests with Chrome DevTools](docs/recipes/debugging-with-chrome-devtools.md)
 - [Debugging tests with VSCode](docs/recipes/debugging-with-vscode.md)
 - [Debugging tests with WebStorm](docs/recipes/debugging-with-webstorm.md)
+- [Debugging tests with node-inspect](docs/recipes/debugging-with-node-inspect.md)
 - [Isolated MongoDB integration tests](docs/recipes/isolated-mongodb-integration-tests.md)
 - [Testing web apps using Puppeteer](docs/recipes/puppeteer.md)