chore(deps): update react monorepo

[renovate[bot]]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@types/react (source)	18.0.27 -> 18.0.28
@types/react-dom (source)	18.0.9 -> 18.0.11
@types/react-dom (source)	18.0.5 -> 18.0.11
react-refresh (source)	^0.10.0 -> ^0.14.0

---

Release Notes

facebook/react

### [`v0.14.0`](https://togithub.com/facebook/react/blob/HEAD/CHANGELOG.md#​0140-October-7-2015) [Compare Source](https://togithub.com/facebook/react/compare/v0.13.0...v0.14.0) ##### Major changes - Split the main `react` package into two: `react` and `react-dom`. This paves the way to writing components that can be shared between the web version of React and React Native. This means you will need to include both files and some functions have been moved from `React` to `ReactDOM`. - Addons have been moved to separate packages (`react-addons-clone-with-props`, `react-addons-create-fragment`, `react-addons-css-transition-group`, `react-addons-linked-state-mixin`, `react-addons-perf`, `react-addons-pure-render-mixin`, `react-addons-shallow-compare`, `react-addons-test-utils`, `react-addons-transition-group`, `react-addons-update`, `ReactDOM.unstable_batchedUpdates`). - Stateless functional components - React components were previously created using React.createClass or using ES6 classes. This release adds a [new syntax](https://reactjs.org/docs/reusable-components.html#stateless-functions) where a user defines a single [stateless render function](https://reactjs.org/docs/reusable-components.html#stateless-functions) (with one parameter: `props`) which returns a JSX element, and this function may be used as a component. - Refs to DOM components as the DOM node itself. Previously the only useful thing you can do with a DOM component is call `getDOMNode()` to get the underlying DOM node. Starting with this release, a ref to a DOM component *is* the actual DOM node. **Note that refs to custom (user-defined) components work exactly as before; only the built-in DOM components are affected by this change.** ##### Breaking changes - `React.initializeTouchEvents` is no longer necessary and has been removed completely. Touch events now work automatically. - Add-Ons: Due to the DOM node refs change mentioned above, `TestUtils.findAllInRenderedTree` and related helpers are no longer able to take a DOM component, only a custom component. - The `props` object is now frozen, so mutating props after creating a component element is no longer supported. In most cases, [`React.cloneElement`](https://reactjs.org/docs/react-api.html#cloneelement) should be used instead. This change makes your components easier to reason about and enables the compiler optimizations mentioned above. - Plain objects are no longer supported as React children; arrays should be used instead. You can use the [`createFragment`](https://reactjs.org/docs/create-fragment.html) helper to migrate, which now returns an array. - Add-Ons: `classSet` has been removed. Use [classnames](https://togithub.com/JedWatson/classnames) instead. - Web components (custom elements) now use native property names. Eg: `class` instead of `className`. ##### Deprecations - `this.getDOMNode()` is now deprecated and `ReactDOM.findDOMNode(this)` can be used instead. Note that in the common case, `findDOMNode` is now unnecessary since a ref to the DOM component is now the actual DOM node. - `setProps` and `replaceProps` are now deprecated. Instead, call ReactDOM.render again at the top level with the new props. - ES6 component classes must now extend `React.Component` in order to enable stateless function components. The [ES3 module pattern](https://reactjs.org/blog/2015/01/27/react-v0.13.0-beta-1.html#other-languages) will continue to work. - Reusing and mutating a `style` object between renders has been deprecated. This mirrors our change to freeze the `props` object. - Add-Ons: `cloneWithProps` is now deprecated. Use [`React.cloneElement`](https://reactjs.org/docs/react-api.html#cloneelement) instead (unlike `cloneWithProps`, `cloneElement` does not merge `className` or `style` automatically; you can merge them manually if needed). - Add-Ons: To improve reliability, `CSSTransitionGroup` will no longer listen to transition events. Instead, you should specify transition durations manually using props such as `transitionEnterTimeout={500}`. ##### Notable enhancements - Added `React.Children.toArray` which takes a nested children object and returns a flat array with keys assigned to each child. This helper makes it easier to manipulate collections of children in your `render` methods, especially if you want to reorder or slice `this.props.children` before passing it down. In addition, `React.Children.map` now returns plain arrays too. - React uses `console.error` instead of `console.warn` for warnings so that browsers show a full stack trace in the console. (Our warnings appear when you use patterns that will break in future releases and for code that is likely to behave unexpectedly, so we do consider our warnings to be “must-fix” errors.) - Previously, including untrusted objects as React children [could result in an XSS security vulnerability](http://danlec.com/blog/xss-via-a-spoofed-react-element). This problem should be avoided by properly validating input at the application layer and by never passing untrusted objects around your application code. As an additional layer of protection, [React now tags elements](https://togithub.com/facebook/react/pull/4832) with a specific [ES2015 (ES6) `Symbol`](http://www.2ality.com/2014/12/es6-symbols.html) in browsers that support it, in order to ensure that React never considers untrusted JSON to be a valid element. If this extra security protection is important to you, you should add a `Symbol` polyfill for older browsers, such as the one included by [Babel’s polyfill](https://babeljs.io/docs/usage/polyfill/). - When possible, React DOM now generates XHTML-compatible markup. - React DOM now supports these standard HTML attributes: `capture`, `challenge`, `inputMode`, `is`, `keyParams`, `keyType`, `minLength`, `summary`, `wrap`. It also now supports these non-standard attributes: `autoSave`, `results`, `security`. - React DOM now supports these SVG attributes, which render into namespaced attributes: `xlinkActuate`, `xlinkArcrole`, `xlinkHref`, `xlinkRole`, `xlinkShow`, `xlinkTitle`, `xlinkType`, `xmlBase`, `xmlLang`, `xmlSpace`. - The `image` SVG tag is now supported by React DOM. - In React DOM, arbitrary attributes are supported on custom elements (those with a hyphen in the tag name or an `is="..."` attribute). - React DOM now supports these media events on `audio` and `video` tags: `onAbort`, `onCanPlay`, `onCanPlayThrough`, `onDurationChange`, `onEmptied`, `onEncrypted`, `onEnded`, `onError`, `onLoadedData`, `onLoadedMetadata`, `onLoadStart`, `onPause`, `onPlay`, `onPlaying`, `onProgress`, `onRateChange`, `onSeeked`, `onSeeking`, `onStalled`, `onSuspend`, `onTimeUpdate`, `onVolumeChange`, `onWaiting`. - Many small performance improvements have been made. - Many warnings show more context than before. - Add-Ons: A [`shallowCompare`](https://togithub.com/facebook/react/pull/3355) add-on has been added as a migration path for `PureRenderMixin` in ES6 classes. - Add-Ons: `CSSTransitionGroup` can now use [custom class names](https://togithub.com/facebook/react/blob/48942b85/docs/docs/10.1-animation.md#custom-classes) instead of appending `-enter-active` or similar to the transition name. ##### New helpful warnings - React DOM now warns you when nesting HTML elements invalidly, which helps you avoid surprising errors during updates. - Passing `document.body` directly as the container to `ReactDOM.render` now gives a warning as doing so can cause problems with browser extensions that modify the DOM. - Using multiple instances of React together is not supported, so we now warn when we detect this case to help you avoid running into the resulting problems. ##### Notable bug fixes - Click events are handled by React DOM more reliably in mobile browsers, particularly in Mobile Safari. - SVG elements are created with the correct namespace in more cases. - React DOM now renders `` elements with multiple text children properly and renders `` elements on the server with the correct option selected. - When two separate copies of React add nodes to the same document (including when a browser extension uses React), React DOM tries harder not to throw exceptions during event handling. - Using non-lowercase HTML tag names in React DOM (e.g., `React.createElement('DIV')`) no longer causes problems, though we continue to recommend lowercase for consistency with the JSX tag name convention (lowercase names refer to built-in components, capitalized names refer to custom components). - React DOM understands that these CSS properties are unitless and does not append “px” to their values: `animationIterationCount`, `boxOrdinalGroup`, `flexOrder`, `tabSize`, `stopOpacity`. - Add-Ons: When using the test utils, `Simulate.mouseEnter` and `Simulate.mouseLeave` now work. - Add-Ons: ReactTransitionGroup now correctly handles multiple nodes being removed simultaneously. ##### React Tools / Babel ##### Breaking Changes - The `react-tools` package and `JSXTransformer.js` browser file [have been deprecated](https://reactjs.org/blog/2015/06/12/deprecating-jstransform-and-react-tools.html). You can continue using version `0.13.3` of both, but we no longer support them and recommend migrating to [Babel](https://babeljs.io), which has built-in support for React and JSX. ##### New Features - Babel 5.8.24 introduces **Inlining React elements:** The `optimisation.react.inlineElements` transform converts JSX elements to object literals like `{type: 'div', props: ...}` instead of calls to `React.createElement`. This should only be enabled in production, since it disables some development warnings/checks. - Babel 5.8.24 introduces **Constant hoisting for React elements:** The `optimisation.react.constantElements` transform hoists element creation to the top level for subtrees that are fully static, which reduces calls to `React.createElement` and the resulting allocations. More importantly, it tells React that the subtree hasn’t changed so React can completely skip it when reconciling. This should only be enabled in production, since it disables some development warnings/checks. ### [`v0.13.0`](https://togithub.com/facebook/react/blob/HEAD/CHANGELOG.md#​0130-March-10-2015) [Compare Source](https://togithub.com/facebook/react/compare/v0.12.0...v0.13.0) ##### React Core ##### Breaking Changes - Deprecated patterns that warned in 0.12 no longer work: most prominently, calling component classes without using JSX or React.createElement and using non-component functions with JSX or createElement - Mutating `props` after an element is created is deprecated and will cause warnings in development mode; future versions of React will incorporate performance optimizations assuming that props aren't mutated - Static methods (defined in `statics`) are no longer autobound to the component class - `ref` resolution order has changed slightly such that a ref to a component is available immediately after its `componentDidMount` method is called; this change should be observable only if your component calls a parent component's callback within your `componentDidMount`, which is an anti-pattern and should be avoided regardless - Calls to `setState` in life-cycle methods are now always batched and therefore asynchronous. Previously the first call on the first mount was synchronous. - `setState` and `forceUpdate` on an unmounted component now warns instead of throwing. That avoids a possible race condition with Promises. - Access to most internal properties has been completely removed, including `this._pendingState` and `this._rootNodeID`. ##### New Features - Support for using ES6 classes to build React components; see the [v0.13.0 beta 1 notes](https://reactjs.org/blog/2015/01/27/react-v0.13.0-beta-1.html) for details. - Added new top-level API `React.findDOMNode(component)`, which should be used in place of `component.getDOMNode()`. The base class for ES6-based components will not have `getDOMNode`. This change will enable some more patterns moving forward. - Added a new top-level API `React.cloneElement(el, props)` for making copies of React elements – see the [v0.13 RC2 notes](https://reactjs.org/blog/2015/03/03/react-v0.13-rc2.html#react.cloneelement) for more details. - New `ref` style, allowing a callback to be used in place of a name: ` this._photo = c} />` allows you to reference the component with `this._photo` (as opposed to `ref="photo"` which gives `this.refs.photo`). - `this.setState()` can now take a function as the first argument for transactional state updates, such as `this.setState((state, props) => ({count: state.count + 1}));` – this means that you no longer need to use `this._pendingState`, which is now gone. - Support for iterators and immutable-js sequences as children. ##### Deprecations - `ComponentClass.type` is deprecated. Just use `ComponentClass` (usually as `element.type === ComponentClass`). - Some methods that are available on `createClass`-based components are removed or deprecated from ES6 classes (`getDOMNode`, `replaceState`, `isMounted`, `setProps`, `replaceProps`). ##### React with Add-Ons ##### New Features - [`React.addons.createFragment` was added](https://reactjs.org/docs/create-fragment.html) for adding keys to entire sets of children. ##### Deprecations - `React.addons.classSet` is now deprecated. This functionality can be replaced with several freely available modules. [classnames](https://www.npmjs.com/package/classnames) is one such module. - Calls to `React.addons.cloneWithProps` can be migrated to use `React.cloneElement` instead – make sure to merge `style` and `className` manually if desired. ##### React Tools ##### Breaking Changes - When transforming ES6 syntax, `class` methods are no longer enumerable by default, which requires `Object.defineProperty`; if you support browsers such as IE8, you can pass `--target es3` to mirror the old behavior ##### New Features - `--target` option is available on the jsx command, allowing users to specify and ECMAScript version to target. - `es5` is the default. - `es3` restores the previous default behavior. An additional transform is added here to ensure the use of reserved words as properties is safe (eg `this.static` will become `this['static']` for IE8 compatibility). - The transform for the call spread operator has also been enabled. ##### JSXTransformer ##### Breaking Changes - The return value of `transform` now contains `sourceMap` as a JS object already, not an instance of `SourceMapGenerator`. ##### JSX ##### Breaking Changes - A change was made to how some JSX was parsed, specifically around the use of `>` or `}` when inside an element. Previously it would be treated as a string but now it will be treated as a parse error. The [`jsx_orphaned_brackets_transformer`](https://www.npmjs.com/package/jsx_orphaned_brackets_transformer) package on npm can be used to find and fix potential issues in your JSX code. ### [`v0.12.0`](https://togithub.com/facebook/react/blob/HEAD/CHANGELOG.md#​0120-October-28-2014) [Compare Source](https://togithub.com/facebook/react/compare/v0.11.0...v0.12.0) ##### React Core ##### Breaking Changes - `key` and `ref` moved off props object, now accessible on the element directly - React is now BSD licensed with accompanying Patents grant - Default prop resolution has moved to Element creation time instead of mount time, making them effectively static - `React.__internals` is removed - it was exposed for DevTools which no longer needs access - Composite Component functions can no longer be called directly - they must be wrapped with `React.createFactory` first. This is handled for you when using JSX. ##### New Features - Spread operator (`{...}`) introduced to deprecate `this.transferPropsTo` - Added support for more HTML attributes: `acceptCharset`, `classID`, `manifest` ##### Deprecations - `React.renderComponent` --> `React.render` - `React.renderComponentToString` --> `React.renderToString` - `React.renderComponentToStaticMarkup` --> `React.renderToStaticMarkup` - `React.isValidComponent` --> `React.isValidElement` - `React.PropTypes.component` --> `React.PropTypes.element` - `React.PropTypes.renderable` --> `React.PropTypes.node` - **DEPRECATED** `React.isValidClass` - **DEPRECATED** `instance.transferPropsTo` - **DEPRECATED** Returning `false` from event handlers to preventDefault - **DEPRECATED** Convenience Constructor usage as function, instead wrap with `React.createFactory` - **DEPRECATED** use of `key={null}` to assign implicit keys ##### Bug Fixes - Better handling of events and updates in nested results, fixing value restoration in "layered" controlled components - Correctly treat `event.getModifierState` as case sensitive - Improved normalization of `event.charCode` - Better error stacks when involving autobound methods - Removed DevTools message when the DevTools are installed - Correctly detect required language features across browsers - Fixed support for some HTML attributes: - `list` updates correctly now - `scrollLeft`, `scrollTop` removed, these should not be specified as props - Improved error messages ##### React With Addons ##### New Features - `React.addons.batchedUpdates` added to API for hooking into update cycle ##### Breaking Changes - `React.addons.update` uses `assign` instead of `copyProperties` which does `hasOwnProperty` checks. Properties on prototypes will no longer be updated correctly. ##### Bug Fixes - Fixed some issues with CSS Transitions ##### JSX ##### Breaking Changes - Enforced convention: lower case tag names are always treated as HTML tags, upper case tag names are always treated as composite components - JSX no longer transforms to simple function calls ##### New Features - `@jsx React.DOM` no longer required - spread (`{...}`) operator introduced to allow easier use of props ##### Bug Fixes - JSXTransformer: Make sourcemaps an option when using APIs directly (eg, for react-rails) ### [`v0.11.0`](https://togithub.com/facebook/react/blob/HEAD/CHANGELOG.md#​0110-July-17-2014) [Compare Source](https://togithub.com/facebook/react/compare/v0.10.0...v0.11.0) ##### React Core ##### Breaking Changes - `getDefaultProps()` is now called once per class and shared across all instances - `MyComponent()` now returns a descriptor, not an instance - `React.isValidComponent` and `React.PropTypes.component` validate *descriptors*, not component instances - Custom `propType` validators should return an `Error` instead of logging directly ##### New Features - Rendering to `null` - Keyboard events include normalized `e.key` and `e.getModifierState()` properties - New normalized `onBeforeInput` event - `React.Children.count` has been added as a helper for counting the number of children ##### Bug Fixes - Re-renders are batched in more cases - Events: `e.view` properly normalized - Added Support for more HTML attributes (`coords`, `crossOrigin`, `download`, `hrefLang`, `mediaGroup`, `muted`, `scrolling`, `shape`, `srcSet`, `start`, `useMap`) - Improved SVG support - Changing `className` on a mounted SVG component now works correctly - Added support for elements `mask` and `tspan` - Added support for attributes `dx`, `dy`, `fillOpacity`, `fontFamily`, `fontSize`, `markerEnd`, `markerMid`, `markerStart`, `opacity`, `patternContentUnits`, `patternUnits`, `preserveAspectRatio`, `strokeDasharray`, `strokeOpacity` - CSS property names with vendor prefixes (`Webkit`, `ms`, `Moz`, `O`) are now handled properly - Duplicate keys no longer cause a hard error; now a warning is logged (and only one of the children with the same key is shown) - `img` event listeners are now unbound properly, preventing the error "Two valid but unequal nodes with the same `data-reactid`" - Added explicit warning when missing polyfills ##### React With Addons - PureRenderMixin: a mixin which helps optimize "pure" components - Perf: a new set of tools to help with performance analysis - Update: New `$apply` command to transform values - TransitionGroup bug fixes with null elements, Android ##### React NPM Module - Now includes the pre-built packages under `dist/`. - `envify` is properly listed as a dependency instead of a peer dependency ##### JSX - Added support for namespaces, eg `` - JSXTransformer - Enable the same `harmony` features available in the command line with ` Githubissues.

Githubissues is a development platform for aggregating issues.