webext-schema 5.2.1 → 5.2.3

package/modules/file-util.js

@@ -7,9 +7,9 @@ import fs, { promises as fsPromise } from 'node:fs';
 import path from 'node:path';
 import { fileURLToPath } from 'node:url';
 import { getType, isString } from './common.js';
-import { IS_WIN } from './constant.js';
 
 /* constants */
+import { IS_WIN } from './constant.js';
 const MASK_BIT = 0o111;
 const PERM_DIR = 0o777;
 const PERM_FILE = 0o666;

package/modules/schema.js

@@ -10,6 +10,8 @@ import decamelize from 'decamelize';
 import sinon from 'sinon';
 import { getType, isObjectNotEmpty, isString } from './common.js';
 import { convertUriToFilePath } from './file-util.js';
+
+/* constants */
 import { CHAR } from './constant.js';
 
 export class Schema {

package/modules/update.js

@@ -8,9 +8,9 @@ import process from 'node:process';
 import JSON5 from 'json5';
 import { getType, isString } from './common.js';
 import { createFile } from './file-util.js';
-import { CHAR, INDENT } from './constant.js';
 
 /* constants */
+import { CHAR, INDENT } from './constant.js';
 const DIR_CWD = process.cwd();
 const PERM_FILE = 0o644;
 export const ESR_VER = 115;

package/package.json

@@ -17,24 +17,24 @@
     "commander": "^11.0.0",
     "decamelize": "^6.0.0",
     "json5": "^2.2.3",
-    "sinon": "^15.2.0"
+    "sinon": "^16.0.0"
   },
   "devDependencies": {
-    "@types/firefox-webext-browser": "^111.0.1",
-    "@types/node": "^20.4.5",
-    "@types/sinon": "^10.0.16",
+    "@types/firefox-webext-browser": "^111.0.2",
+    "@types/node": "^20.7.0",
+    "@types/sinon": "^10.0.17",
     "c8": "^8.0.1",
-    "chai": "^4.3.7",
-    "eslint": "^8.46.0",
+    "chai": "^4.3.8",
+    "eslint": "^8.50.0",
     "eslint-config-standard": "^17.1.0",
-    "eslint-plugin-import": "^2.28.0",
-    "eslint-plugin-jsdoc": "^46.4.5",
+    "eslint-plugin-import": "^2.28.1",
+    "eslint-plugin-jsdoc": "^46.8.2",
     "eslint-plugin-regexp": "^1.15.0",
     "eslint-plugin-unicorn": "^48.0.1",
     "mocha": "^10.2.0",
     "npm-run-all": "^4.1.5",
-    "typescript": "^5.1.6",
-    "undici": "^5.22.1"
+    "typescript": "^5.2.2",
+    "undici": "^5.25.2"
   },
   "scripts": {
     "build": "npm run tsc && npm run lint && npm run test",
@@ -54,5 +54,5 @@
     "update-mail": "node index update --channel=mail -i",
     "update-release": "node index update --channel=release -i"
   },
-  "version": "5.2.1"
+  "version": "5.2.3"
 }

package/schemas/beta/webext.json

@@ -12575,7 +12575,8 @@
             "unregisteredthreads",
             "processcpu",
             "power",
-            "responsiveness"
+            "responsiveness",
+            "cpufreq"
           ]
         },
         {

package/schemas/central/webext.json

@@ -12575,7 +12575,8 @@
             "unregisteredthreads",
             "processcpu",
             "power",
-            "responsiveness"
+            "responsiveness",
+            "cpufreq"
           ]
         },
         {

package/schemas/mail/mailext.json

@@ -10926,20 +10926,58 @@
         {
           "name": "getRaw",
           "type": "function",
-          "description": "Returns the unmodified source of a message as a `binary string <|link-binary-string|>`__, which is a simple series of 8-bit values. Throws if the message could not be read, for example due to network issues. If the message contains non-ASCII characters, the body parts in the binary string cannot be read directly and must be decoded according to their character sets. Use :ref:`messages.getFull` to get the correctly decoded parts. Manually decoding the raw message is probably too error-prone, especially if the message contains MIME parts with different character set encodings or attachments.\n\nTo get a readable version of the raw message as it appears in Thunderbird's message source view, it may be sufficient to decode the message according to the character set specified in its main `content-type <|link-content-type|>`__ header (example: <value>text/html; charset=UTF-8</value>) using the following function (see MDN for `supported input encodings <|link-input-encoding|>`__): <literalinclude>includes/messages/decodeBinaryString.js<lang>JavaScript</lang></literalinclude>",
+          "description": "Returns the unmodified source of a message. Throws if the message could not be read, for example due to network issues.",
           "async": "callback",
           "parameters": [
             {
               "name": "messageId",
               "type": "integer"
             },
+            {
+              "name": "options",
+              "type": "object",
+              "properties": {
+                "data_format": {
+                  "choices": [
+                    {
+                      "max_manifest_version": 2,
+                      "description": "The message can either be returned as a DOM File or as a `binary string <|link-binary-string|>`__. The historic default is to return a binary string (kept for backward compatibility). However, it is now recommended to use the ``File`` format, because the DOM File object can be used as-is with the downloads API and has useful methods to access the content, like `File.text() <|link-DOMFile-text|>`__ and `File.arrayBuffer() <|link-DOMFile-arrayBuffer|>`__. Working with binary strings is error prone and needs special handling: <literalinclude>includes/messages/decodeBinaryString.js<lang>JavaScript</lang></literalinclude> (see MDN for `supported input encodings <|link-input-encoding|>`__).",
+                      "type": "string",
+                      "enum": [
+                        "File",
+                        "BinaryString"
+                      ]
+                    },
+                    {
+                      "min_manifest_version": 3,
+                      "description": "The message can either be returned as a DOM File (default) or as a `binary string <|link-binary-string|>`__. It is recommended to use the ``File`` format, because the DOM File object can be used as-is with the downloads API and has useful methods to access the content, like `File.text() <|link-DOMFile-text|>`__ and `File.arrayBuffer() <|link-DOMFile-arrayBuffer|>`__. Working with binary strings is error prone and needs special handling: <literalinclude>includes/messages/decodeBinaryString.js<lang>JavaScript</lang></literalinclude> (see MDN for `supported input encodings <|link-input-encoding|>`__).",
+                      "type": "string",
+                      "enum": [
+                        "File",
+                        "BinaryString"
+                      ]
+                    }
+                  ]
+                }
+              },
+              "optional": true
+            },
             {
               "type": "function",
               "name": "callback",
               "optional": true,
               "parameters": [
                 {
-                  "type": "string"
+                  "choices": [
+                    {
+                      "type": "string"
+                    },
+                    {
+                      "type": "object",
+                      "isInstanceOf": "File",
+                      "additionalProperties": true
+                    }
+                  ]
                 }
               ]
             }

package/schemas/release/webext.json

@@ -12575,7 +12575,8 @@
             "unregisteredthreads",
             "processcpu",
             "power",
-            "responsiveness"
+            "responsiveness",
+            "cpufreq"
           ]
         },
         {