From 8a3f6cad1de3a892940f51474a33b5e2544c7745 Mon Sep 17 00:00:00 2001 From: Sindre Sorhus Date: Thu, 2 May 2019 13:32:28 +0700 Subject: [PATCH] Remove mention of the obsolete `devtool` package See https://github.com/Jam3/devtool Closes #989 --- maintaining.md | 11 ++--------- 1 file changed, 2 insertions(+), 9 deletions(-) diff --git a/maintaining.md b/maintaining.md index 00c3be6f0..4b13fea8c 100644 --- a/maintaining.md +++ b/maintaining.md @@ -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`](https://github.com/s-a/iron-node) and / or [`devtool`](https://github.com/Jam3/devtool) globally: +You should first install [`iron-node`](https://github.com/s-a/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 ``` -Or: - -``` -$ devtool node_modules/ava/profile.js -``` - Once the Dev Tools window has loaded, activate Memory or CPU profiling, and then hit Cmd R 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`](http://mattdesl.svbtle.com/debugging-nodejs-in-chrome-devtools). - [A video introduction to Chrome DevTools CPU and Memory profiling](https://www.youtube.com/watch?v=KKwmdTByxLk).