fix as suggest.

Author: ShuiRuTian

README.md

@@ -103,4 +103,4 @@ To give you a sense of whether we will accept changes, you can use these heurist
 - `overridingTypes.json`: types that are defined in the spec file but has a better or more up-to-date definitions in the json files.
 - `removedTypes.json`: types that are defined in the spec file but should be removed.
 - `comments.json`: comment strings to be embedded in the generated .js files.
-- `deprecatedMessage.json`: the reason why one type is deprecated. The reason why it is a sprecate file rather than merge in comment.json is mdn/apiDescriptions.json would also possiably be deprecated.
+- `deprecatedMessage.json`: the reason why one type is deprecated. The reason why it is a separate file rather than merge in comment.json is mdn/apiDescriptions.json would also possibly be deprecated.

manualAnalytics/README.md

@@ -19,7 +19,6 @@
     "node-fetch": "^2.6.0",
     "print-diff": "^0.1.1",
     "styleless-innertext": "^1.1.2",
-    "ts-node": "^8.10.2",
     "typescript": "next",
     "webidl2": "^23.12.1"
   }

manualAnalytics/idlSourceAppearDeprecateText.ts

@@ -116,9 +116,9 @@ function emitDom() {
         for (const [key, value] of Object.entries(descriptions)) {
             const target = idl.interfaces!.interface[key] || namespaces[key];
             if (target) {
-                const tmp = target.comment ?? "";
-                const tmp2 = "\n * @deprecated " + transformVerbosity(key, value);
-                target.comment = tmp + tmp2;
+                const comment = target.comment ?? "";
+                const deprecated = "\n * @deprecated " + transformVerbosity(key, value);
+                target.comment = comment + deprecated;
             }
         }
         return idl;