Merge pull request #230 from TracerBench/update-remark

[chore] update remark

Author: krisselden

README.md

@@ -9,27 +9,27 @@ designed with automation in mind.
 
 ## Table of Contents
 
--   [Features](#features)
+*   [Features](#features)
 
--   [Examples](#examples)
+*   [Examples](#examples)
 
-    -   [Print URL as PDF](#print-url-as-pdf)
-    -   [Node Debugging](#node-debugging)
+    *   [Print URL as PDF](#print-url-as-pdf)
+    *   [Node Debugging](#node-debugging)
 
 ## Features
 
--   Promise API for async/await (most debugger commands are meant to be sequential).
--   TypeScript support and uses "devtools-protocol" types, allowing you to pick a protocol version.
--   Launches Chrome with a new temp user data folder so Chrome launches an isolated instance.
+*   Promise API for async/await (most debugger commands are meant to be sequential).
+*   TypeScript support and uses "devtools-protocol" types, allowing you to pick a protocol version.
+*   Launches Chrome with a new temp user data folder so Chrome launches an isolated instance.
     (regardless if you already have Chrome open).
--   Opens Chrome with a pipe message transport to the browser connection and supports
+*   Opens Chrome with a pipe message transport to the browser connection and supports
     attaching flattened session connections to targets.
--   Supports cancellation in a way that avoids unhandled rejections, and allows you to add combine
+*   Supports cancellation in a way that avoids unhandled rejections, and allows you to add combine
     additional cancellation concerns.
--   Supports seeing protocol debug messages with `DEBUG=chrome-debugging-client:*`
--   Use with race-cancellation library to add timeouts or other cancellation concerns to tasks
+*   Supports seeing protocol debug messages with `DEBUG=chrome-debugging-client:*`
+*   Use with race-cancellation library to add timeouts or other cancellation concerns to tasks
     using the connection.
--   The library was designed to be careful about not floating promises (promises are
+*   The library was designed to be careful about not floating promises (promises are
     chained immediately after being created, combining concurrent promises with all
     or race), this avoids unhandled rejections.
 

chrome-debugging-client/README.md

@@ -9,27 +9,27 @@ designed with automation in mind.
 
 ## Table of Contents
 
--   [Features](#features)
+*   [Features](#features)
 
--   [Examples](#examples)
+*   [Examples](#examples)
 
-    -   [Print URL as PDF](#print-url-as-pdf)
-    -   [Node Debugging](#node-debugging)
+    *   [Print URL as PDF](#print-url-as-pdf)
+    *   [Node Debugging](#node-debugging)
 
 ## Features
 
--   Promise API for async/await (most debugger commands are meant to be sequential).
--   TypeScript support and uses "devtools-protocol" types, allowing you to pick a protocol version.
--   Launches Chrome with a new temp user data folder so Chrome launches an isolated instance.
+*   Promise API for async/await (most debugger commands are meant to be sequential).
+*   TypeScript support and uses "devtools-protocol" types, allowing you to pick a protocol version.
+*   Launches Chrome with a new temp user data folder so Chrome launches an isolated instance.
     (regardless if you already have Chrome open).
--   Opens Chrome with a pipe message transport to the browser connection and supports
+*   Opens Chrome with a pipe message transport to the browser connection and supports
     attaching flattened session connections to targets.
--   Supports cancellation in a way that avoids unhandled rejections, and allows you to add combine
+*   Supports cancellation in a way that avoids unhandled rejections, and allows you to add combine
     additional cancellation concerns.
--   Supports seeing protocol debug messages with `DEBUG=chrome-debugging-client:*`
--   Use with race-cancellation library to add timeouts or other cancellation concerns to tasks
+*   Supports seeing protocol debug messages with `DEBUG=chrome-debugging-client:*`
+*   Use with race-cancellation library to add timeouts or other cancellation concerns to tasks
     using the connection.
--   The library was designed to be careful about not floating promises (promises are
+*   The library was designed to be careful about not floating promises (promises are
     chained immediately after being created, combining concurrent promises with all
     or race), this avoids unhandled rejections.
 

scripts/package.json

@@ -9,10 +9,10 @@
   },
   "dependencies": {
     "@types/node": "^18.16.0",
-    "remark": "^12.0.0",
-    "remark-parse": "^8.0.2",
-    "remark-stringify": "^8.0.0",
-    "remark-toc": "^7.0.0",
+    "remark": "^14.0.2",
+    "remark-parse": "^10.0.1",
+    "remark-stringify": "^10.0.2",
+    "remark-toc": "^8.0.1",
     "shell-split": "^1.0.0",
     "unified": "^9.0.0",
     "unist-util-visit": "^2.0.0",

scripts/readme.js

@@ -2,16 +2,16 @@
 const fs = require("fs");
 const path = require("path");
 const unified = require("unified");
-const parse = require("remark-parse");
-const stringify = require("remark-stringify");
-const toc = require("remark-toc");
 const vfile = require("vfile");
 
 const importCode = require("./import-code");
 
 void main();
 
 async function main() {
+  const { default: parse } = await import("remark-parse");
+  const { default: stringify } = await import("remark-stringify");
+  const { default: toc } = await import("remark-toc");
   const processor = unified()
     .use(parse)
     .use(toc)