chrome-types 0.1.397 → 0.1.399

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. package/_all.d.ts +4 -6
  2. package/index.d.ts +4 -6
  3. package/package.json +2 -2
package/_all.d.ts CHANGED
@@ -14,8 +14,8 @@
14
14
  * limitations under the License.
15
15
  */
16
16
 
17
- // Generated on Mon Dec 15 2025 22:33:47 GMT+0000 (Coordinated Universal Time)
18
- // Built at 03f290c5a6801ea2179d32674cfc8f40a9edae8e
17
+ // Generated on Wed Dec 17 2025 22:33:51 GMT+0000 (Coordinated Universal Time)
18
+ // Built at 2d06b4c65786e0e17bc0bc475967fdc6e73d810f
19
19
 
20
20
  // Includes all types, including MV2 + Platform Apps APIs.
21
21
 
@@ -25236,6 +25236,7 @@ declare namespace chrome {
25236
25236
  *
25237
25237
  * @param extensionId The ID of the extension to send the message to. If omitted, the message will be sent to your own extension/app. Required if sending messages from a web page for [web messaging](https://developer.chrome.com/docs/extensions/manifest/externally_connectable).
25238
25238
  * @param message The message to send. This message should be a JSON-ifiable object.
25239
+ * @param callback Promise support was added for extension contexts in Chrome 99. When communicating from a web page to an extension, promises are available from Chrome 118.
25239
25240
  */
25240
25241
  export function sendMessage(
25241
25242
 
@@ -25264,6 +25265,7 @@ declare namespace chrome {
25264
25265
  * Sends a single message to event listeners within your extension or a different extension/app. Similar to {@link runtime.connect} but only sends a single message, with an optional response. If sending to your extension, the {@link runtime.onMessage} event will be fired in every frame of your extension (except for the sender's frame), or {@link runtime.onMessageExternal}, if a different extension. Note that extensions cannot send messages to content scripts using this method. To send messages to content scripts, use {@link tabs.sendMessage}.
25265
25266
  *
25266
25267
  * @param message The message to send. This message should be a JSON-ifiable object.
25268
+ * @param callback Promise support was added for extension contexts in Chrome 99. When communicating from a web page to an extension, promises are available from Chrome 118.
25267
25269
  */
25268
25270
  export function sendMessage(
25269
25271
 
@@ -26453,10 +26455,6 @@ declare namespace chrome {
26453
26455
  * Use the `chrome.sessions` API to query and restore tabs and windows from a browsing session.
26454
26456
  *
26455
26457
  * @chrome-permission sessions
26456
- * @chrome-platform chromeos
26457
- * @chrome-platform linux
26458
- * @chrome-platform mac
26459
- * @chrome-platform win
26460
26458
  */
26461
26459
  export namespace sessions {
26462
26460
 
package/index.d.ts CHANGED
@@ -14,8 +14,8 @@
14
14
  * limitations under the License.
15
15
  */
16
16
 
17
- // Generated on Mon Dec 15 2025 22:33:42 GMT+0000 (Coordinated Universal Time)
18
- // Built at 03f290c5a6801ea2179d32674cfc8f40a9edae8e
17
+ // Generated on Wed Dec 17 2025 22:33:46 GMT+0000 (Coordinated Universal Time)
18
+ // Built at 2d06b4c65786e0e17bc0bc475967fdc6e73d810f
19
19
 
20
20
  // Includes MV3+ APIs only.
21
21
 
@@ -17946,6 +17946,7 @@ declare namespace chrome {
17946
17946
  *
17947
17947
  * @param extensionId The ID of the extension to send the message to. If omitted, the message will be sent to your own extension/app. Required if sending messages from a web page for [web messaging](https://developer.chrome.com/docs/extensions/manifest/externally_connectable).
17948
17948
  * @param message The message to send. This message should be a JSON-ifiable object.
17949
+ * @param callback Promise support was added for extension contexts in Chrome 99. When communicating from a web page to an extension, promises are available from Chrome 118.
17949
17950
  */
17950
17951
  export function sendMessage(
17951
17952
 
@@ -17974,6 +17975,7 @@ declare namespace chrome {
17974
17975
  * Sends a single message to event listeners within your extension or a different extension/app. Similar to {@link runtime.connect} but only sends a single message, with an optional response. If sending to your extension, the {@link runtime.onMessage} event will be fired in every frame of your extension (except for the sender's frame), or {@link runtime.onMessageExternal}, if a different extension. Note that extensions cannot send messages to content scripts using this method. To send messages to content scripts, use {@link tabs.sendMessage}.
17975
17976
  *
17976
17977
  * @param message The message to send. This message should be a JSON-ifiable object.
17978
+ * @param callback Promise support was added for extension contexts in Chrome 99. When communicating from a web page to an extension, promises are available from Chrome 118.
17977
17979
  */
17978
17980
  export function sendMessage(
17979
17981
 
@@ -18545,10 +18547,6 @@ declare namespace chrome {
18545
18547
  * Use the `chrome.sessions` API to query and restore tabs and windows from a browsing session.
18546
18548
  *
18547
18549
  * @chrome-permission sessions
18548
- * @chrome-platform chromeos
18549
- * @chrome-platform linux
18550
- * @chrome-platform mac
18551
- * @chrome-platform win
18552
18550
  */
18553
18551
  export namespace sessions {
18554
18552
 
package/package.json CHANGED
@@ -5,7 +5,7 @@
5
5
  "type": "module",
6
6
  "name": "chrome-types",
7
7
  "config": {
8
- "build-hash": "ba512e5dbf10627b"
8
+ "build-hash": "35a39380ace1c11a"
9
9
  },
10
10
  "repository": {
11
11
  "type": "git",
@@ -16,5 +16,5 @@
16
16
  "url": "https://github.com/GoogleChrome/chrome-types/issues"
17
17
  },
18
18
  "homepage": "https://github.com/GoogleChrome/chrome-types",
19
- "version": "0.1.397"
19
+ "version": "0.1.399"
20
20
  }