@types/react-dom 18.2.16 → 18.2.17

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.
react-dom/README.md CHANGED
@@ -8,7 +8,7 @@ This package contains type definitions for react-dom (https://reactjs.org).
8
8
  Files were exported from https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/react-dom.
9
9
 
10
10
  ### Additional Details
11
- * Last updated: Mon, 20 Nov 2023 23:36:24 GMT
11
+ * Last updated: Wed, 22 Nov 2023 00:24:48 GMT
12
12
  * Dependencies: [@types/react](https://npmjs.com/package/@types/react)
13
13
 
14
14
  # Credits
react-dom/index.d.ts CHANGED
@@ -53,6 +53,7 @@ export function unstable_renderSubtreeIntoContainer<P>(
53
53
  element: ReactElement<P>,
54
54
  container: Element,
55
55
  callback?: (component?: Component<P, ComponentState> | Element) => any,
56
+ // eslint-disable-next-line @typescript-eslint/no-invalid-void-type
56
57
  ): Component<P, ComponentState> | Element | void;
57
58
 
58
59
  export type Container = Element | Document | DocumentFragment;
@@ -95,11 +96,13 @@ export interface Renderer {
95
96
  element: ReactElement<P>,
96
97
  container: Container | null,
97
98
  callback?: () => void,
99
+ // eslint-disable-next-line @typescript-eslint/no-invalid-void-type
98
100
  ): Component<P, ComponentState> | Element | void;
99
101
 
100
102
  (
101
103
  element: ReactElement[],
102
104
  container: Container | null,
103
105
  callback?: () => void,
106
+ // eslint-disable-next-line @typescript-eslint/no-invalid-void-type
104
107
  ): Component<any, ComponentState> | Element | void;
105
108
  }
react-dom/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@types/react-dom",
3
- "version": "18.2.16",
3
+ "version": "18.2.17",
4
4
  "description": "TypeScript definitions for react-dom",
5
5
  "homepage": "https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/react-dom",
6
6
  "license": "MIT",
@@ -82,6 +82,6 @@
82
82
  "dependencies": {
83
83
  "@types/react": "*"
84
84
  },
85
- "typesPublisherContentHash": "92e8a0c4e89d1016692884d247bc1cef054510a6ce006161bda93a48c509af2c",
85
+ "typesPublisherContentHash": "10999f1af5ef34daa32af5a8ea57d6fda5371b0e2892ba6820aa49f96306cf12",
86
86
  "typeScriptVersion": "4.5"
87
87
  }
@@ -358,7 +358,7 @@ export function createRenderer(): ShallowRenderer;
358
358
  // `strictNullChecks: false`.
359
359
  // - VoidOrUndefinedOnly is there to forbid any non-void return values for users with `strictNullChecks: true`
360
360
  declare const UNDEFINED_VOID_ONLY: unique symbol;
361
- // tslint:disable-next-line: void-return
361
+ // eslint-disable-next-line @typescript-eslint/no-invalid-void-type
362
362
  type VoidOrUndefinedOnly = void | { [UNDEFINED_VOID_ONLY]: never };
363
363
  // While act does always return Thenable, if a void function is passed, we pretend the return value is also void to not trigger dangling Promise lint rules.
364
364
  export function act(callback: () => VoidOrUndefinedOnly): void;