Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update react monorepo #11

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Update react monorepo #11

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Mar 26, 2022

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@types/react (source) 16.9.35 -> 16.14.62 age adoption passing confidence
@types/react-dom (source) 16.9.8 -> 16.9.24 age adoption passing confidence
react (source) ^0.13.3 -> ^0.14.0 age adoption passing confidence
react (source) 16.13.0 -> 16.14.0 age adoption passing confidence
react (source) 16.13.1 -> 16.14.0 age adoption passing confidence
react (source) ^0.12.2 -> ^0.14.0 age adoption passing confidence
react-dom (source) 16.13.0 -> 16.14.0 age adoption passing confidence
react-dom (source) 16.13.1 -> 16.14.0 age adoption passing confidence

Release Notes

facebook/react (react)

v0.14.10

React

v0.14.8

Compare Source

React
  • Fixed memory leak when rendering on the server

v0.14.7

Compare Source

React
  • Fixed bug with <option> tags when using dangerouslySetInnerHTML
  • Fixed memory leak in synthetic event system
React TestUtils Add-on
  • Fixed bug with calling setState in componentWillMount when using shallow rendering

v0.14.6

Compare Source

React
  • Updated fbjs dependency to pick up change affecting handling of undefined document.

v0.14.5

Compare Source

React
  • More minor internal changes for better compatibility with React Native

v0.14.4

Compare Source

React
  • Minor internal changes for better compatibility with React Native
React DOM
  • The autoCapitalize and autoCorrect props are now set as attributes in the DOM instead of properties to improve cross-browser compatibility
  • Fixed bug with controlled <select> elements not handling updates properly
React Perf Add-on
  • Some DOM operation names have been updated for clarity in the output of .printDOM()

v0.14.3

Compare Source

React DOM
  • Added support for nonce attribute for <script> and <style> elements
  • Added support for reversed attribute for <ol> elements
React TestUtils Add-on
  • Fixed bug with shallow rendering and function refs
React CSSTransitionGroup Add-on
  • Fixed bug resulting in timeouts firing incorrectly when mounting and unmounting rapidly
React on Bower
  • Added react-dom-server.js to expose renderToString and renderToStaticMarkup for usage in the browser

v0.14.2

Compare Source

React DOM
  • Fixed bug with development build preventing events from firing in some versions of Internet Explorer & Edge
  • Fixed bug with development build when using es5-sham in older versions of Internet Explorer
  • Added support for integrity attribute
  • Fixed bug resulting in children prop being coerced to a string for custom elements, which was not the desired behavior
  • Moved react from dependencies to peerDependencies to match expectations and align with react-addons-* packages

v0.14.1

Compare Source

React

v0.14.0

Compare Source

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 where a user defines a single stateless render function (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 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 helper to migrate, which now returns an array.
  • Add-Ons: classSet has been removed. Use 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 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 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. 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 with a specific ES2015 (ES6) Symbol 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.
  • 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 add-on has been added as a migration path for PureRenderMixin in ES6 classes.
  • Add-Ons: CSSTransitionGroup can now use custom class names 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 <option> elements with multiple text children properly and renders <select> 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. You can continue using version 0.13.3 of both, but we no longer support them and recommend migrating to Babel, 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.

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot changed the title Update react monorepo Update dependency react to ^0.14.0 Nov 20, 2022
@renovate renovate bot force-pushed the renovate/react-monorepo branch from 0d22bc7 to 0dc4ab7 Compare March 16, 2023 09:04
@renovate renovate bot changed the title Update dependency react to ^0.14.0 Update react monorepo Mar 16, 2023
@renovate renovate bot force-pushed the renovate/react-monorepo branch 2 times, most recently from ba88dfb to 76ff108 Compare March 28, 2023 03:48
@renovate renovate bot force-pushed the renovate/react-monorepo branch from 76ff108 to 0316f2f Compare March 30, 2023 13:53
@renovate renovate bot force-pushed the renovate/react-monorepo branch from 0316f2f to fd9c437 Compare May 29, 2023 23:42
@renovate renovate bot force-pushed the renovate/react-monorepo branch 2 times, most recently from b8af3e4 to cd23d1a Compare June 10, 2023 09:03
@renovate renovate bot force-pushed the renovate/react-monorepo branch 2 times, most recently from 1cee65d to 52ed11d Compare June 22, 2023 06:03
@renovate renovate bot force-pushed the renovate/react-monorepo branch from 52ed11d to 8a9490d Compare June 30, 2023 03:01
@renovate renovate bot force-pushed the renovate/react-monorepo branch 2 times, most recently from 882f3aa to fe95940 Compare July 11, 2023 02:52
@renovate renovate bot force-pushed the renovate/react-monorepo branch 2 times, most recently from 36e40cc to f121e14 Compare July 19, 2023 20:59
@renovate renovate bot force-pushed the renovate/react-monorepo branch from f121e14 to 3b688b1 Compare July 30, 2023 05:46
@renovate renovate bot force-pushed the renovate/react-monorepo branch 2 times, most recently from 8dd6de8 to c91b104 Compare August 10, 2023 02:58
@renovate renovate bot force-pushed the renovate/react-monorepo branch 2 times, most recently from 5e76893 to dd3ce7f Compare September 27, 2023 02:10
@renovate renovate bot force-pushed the renovate/react-monorepo branch 2 times, most recently from 871d7c0 to 99b9c8b Compare October 2, 2023 05:16
@renovate renovate bot force-pushed the renovate/react-monorepo branch 2 times, most recently from 23209f9 to 30b3a8f Compare November 22, 2023 08:45
@renovate renovate bot force-pushed the renovate/react-monorepo branch 2 times, most recently from b9cb641 to ed3507e Compare February 4, 2024 14:22
@renovate renovate bot force-pushed the renovate/react-monorepo branch 2 times, most recently from 0a88002 to 34ef9f9 Compare February 26, 2024 06:04
@renovate renovate bot force-pushed the renovate/react-monorepo branch 3 times, most recently from 088514a to 2477b7b Compare March 19, 2024 20:54
@renovate renovate bot force-pushed the renovate/react-monorepo branch 3 times, most recently from ac055d4 to 25dd63e Compare March 28, 2024 02:51
@renovate renovate bot force-pushed the renovate/react-monorepo branch 2 times, most recently from af38314 to 90c3ddf Compare April 22, 2024 20:50
@renovate renovate bot force-pushed the renovate/react-monorepo branch from 90c3ddf to 9f56530 Compare April 26, 2024 20:47
@renovate renovate bot force-pushed the renovate/react-monorepo branch from 9f56530 to e7bd5ec Compare June 4, 2024 17:52
@renovate renovate bot force-pushed the renovate/react-monorepo branch from e7bd5ec to 04c2426 Compare July 22, 2024 05:52
@renovate renovate bot force-pushed the renovate/react-monorepo branch from 04c2426 to 04880ef Compare August 9, 2024 23:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants