Skip to content
Browse files

Remove mention of the obsolete `devtool` package

  • Loading branch information...
sindresorhus committed May 2, 2019
1 parent e60c54e commit 8a3f6cad1de3a892940f51474a33b5e2544c7745
Showing with 2 additions and 9 deletions.
  1. +2 −9
@@ -56,10 +56,10 @@ Use the `assigned` label when somebody is working on the issue so we can avoid d

## Profiling

You should first install [`iron-node`]( and / or [`devtool`]( globally:
You should first install [`iron-node`]( globally:

$ npm install --global iron-node devtool
$ npm install --global iron-node

In the root of a project using AVA, run:
@@ -68,12 +68,6 @@ In the root of a project using AVA, run:
$ iron-node node_modules/ava/profile.js <test-file>


$ devtool node_modules/ava/profile.js <test-file>

Once the Dev Tools window has loaded, activate Memory or CPU profiling, and then hit <kbd>Cmd</kbd> <kbd>R</kbd> to rerun the tests.

As soon as the tests finish, stop the recording and inspect the profiler results. The flamegraph can be displayed by choosing `Chart` from the drop down on the `Profiles` tab (other views include `Tree (top down)` and `Heavy (bottom up)`).
@@ -82,7 +76,6 @@ You may also want to check out the Settings page in Dev Tools and enable one or

##### Helpful resources

- [An introduction to Node.js debugging with `devtool`](
- [A video introduction to Chrome DevTools CPU and Memory profiling](

0 comments on commit 8a3f6ca

Please sign in to comment.
You can’t perform that action at this time.