chore: fix linter

nodejs · May 5, 2022 · 1a1a16e · 1a1a16e
1 parent ff60f9a
commit 1a1a16e
Showing 1 changed file with 7 additions and 2 deletions.
diff --git a/locale/en/docs/guides/diagnosis-memory-leak.md b/locale/en/docs/guides/diagnosis-memory-leak.md
@@ -34,7 +34,12 @@ server.get('/write', () => {
   const date = new Date().toString();
 
   // don't do this at home
-  entries.add({ date, arch: os.arch(), platform: os.platform(), cpus: os.cpus() });
+  entries.add({
+    date,
+    arch: os.arch(),
+    platform: os.platform(),
+    cpus: os.cpus()
+  });
 
   return true;
 });
@@ -213,7 +218,7 @@ An excellent way to inspect memory is to make heap dumps and compare them. So le
 import v8 from 'v8';
 
 // then add:
-server.get('/heap-dump/:id',  (req) => {
+server.get('/heap-dump/:id', (req) => {
   const id = req.params.id;
   return v8.writeHeapSnapshot(`heap-dump-${id}.heapsnapshot`);
 });