chore(deps): Update react monorepo to v0.14.10 (next) #4123
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
renovate
bot
force-pushed
the
renovate/next-react-monorepo
branch
from
352e381
to
aae581c
Compare
renovate
bot
force-pushed
the
renovate/next-react-monorepo
branch
2 times, most recently
from
5815c1b
to
3e6831c
Compare
renovate
bot
force-pushed
the
renovate/next-react-monorepo
branch
5 times, most recently
from
66c18f8
to
03c82ad
Compare
renovate
bot
force-pushed
the
renovate/next-react-monorepo
branch
2 times, most recently
from
74e8ad0
to
3cdf03b
Compare
renovate
bot
force-pushed
the
renovate/next-react-monorepo
branch
3 times, most recently
from
0f03e89
to
be9cad6
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## next #4123 +/- ##
==========================================
+ Coverage 95.03% 95.27% +0.23%
==========================================
Files 202 198 -4
Lines 8660 8439 -221
Branches 1627 1578 -49
==========================================
- Hits 8230 8040 -190
+ Misses 325 306 -19
+ Partials 105 93 -12 |
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/next-react-monorepo
branch
from
be9cad6
to
75b1922
Compare
renovate
bot
force-pushed
the
renovate/next-react-monorepo
branch
from
75b1922
to
1cc5d9e
Compare
renovate
bot
force-pushed
the
renovate/next-react-monorepo
branch
2 times, most recently
from
d0ed03b
to
5924fea
Compare
renovate
bot
force-pushed
the
renovate/next-react-monorepo
branch
2 times, most recently
from
8517adf
to
e7eb0a9
Compare
renovate
bot
force-pushed
the
renovate/next-react-monorepo
branch
2 times, most recently
from
5a2050d
to
22c19b9
Compare
renovate
bot
force-pushed
the
renovate/next-react-monorepo
branch
from
22c19b9
to
ddfc357
Compare
|
Important Review skippedBot user detected. To trigger a single review, invoke the You can disable this status message by setting the 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
0.0.0-experimental-ee8509801-20230117->0.14.100.0.0-experimental-ee8509801-20230117->0.14.10Release Notes
facebook/react (react)
v0.14.10React
v0.14.8Compare Source
React
v0.14.7Compare Source
React
<option>tags when usingdangerouslySetInnerHTMLReact TestUtils Add-on
setStateincomponentWillMountwhen using shallow renderingv0.14.6Compare Source
React
fbjsdependency to pick up change affecting handling of undefined document.v0.14.5Compare Source
React
v0.14.4Compare Source
React
React DOM
autoCapitalizeandautoCorrectprops are now set as attributes in the DOM instead of properties to improve cross-browser compatibility<select>elements not handling updates properlyReact Perf Add-on
.printDOM()v0.14.3Compare Source
React DOM
nonceattribute for<script>and<style>elementsreversedattribute for<ol>elementsReact TestUtils Add-on
React CSSTransitionGroup Add-on
React on Bower
react-dom-server.jsto exposerenderToStringandrenderToStaticMarkupfor usage in the browserv0.14.2Compare Source
React DOM
integrityattributechildrenprop being coerced to a string for custom elements, which was not the desired behaviorreactfromdependenciestopeerDependenciesto match expectations and align withreact-addons-*packagesv0.14.1Compare Source
React
v0.14.0Compare Source
Major changes
reactpackage into two:reactandreact-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 fromReacttoReactDOM.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).props) which returns a JSX element, and this function may be used as a component.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.initializeTouchEventsis no longer necessary and has been removed completely. Touch events now work automatically.TestUtils.findAllInRenderedTreeand related helpers are no longer able to take a DOM component, only a custom component.propsobject is now frozen, so mutating props after creating a component element is no longer supported. In most cases,React.cloneElementshould be used instead. This change makes your components easier to reason about and enables the compiler optimizations mentioned above.createFragmenthelper to migrate, which now returns an array.classSethas been removed. Use classnames instead.classinstead ofclassName.Deprecations
this.getDOMNode()is now deprecated andReactDOM.findDOMNode(this)can be used instead. Note that in the common case,findDOMNodeis now unnecessary since a ref to the DOM component is now the actual DOM node.setPropsandreplacePropsare now deprecated. Instead, call ReactDOM.render again at the top level with the new props.React.Componentin order to enable stateless function components. The ES3 module pattern will continue to work.styleobject between renders has been deprecated. This mirrors our change to freeze thepropsobject.cloneWithPropsis now deprecated. UseReact.cloneElementinstead (unlikecloneWithProps,cloneElementdoes not mergeclassNameorstyleautomatically; you can merge them manually if needed).CSSTransitionGroupwill no longer listen to transition events. Instead, you should specify transition durations manually using props such astransitionEnterTimeout={500}.Notable enhancements
React.Children.toArraywhich 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 yourrendermethods, especially if you want to reorder or slicethis.props.childrenbefore passing it down. In addition,React.Children.mapnow returns plain arrays too.console.errorinstead ofconsole.warnfor 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.)Symbolin 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 aSymbolpolyfill for older browsers, such as the one included by Babel’s polyfill.capture,challenge,inputMode,is,keyParams,keyType,minLength,summary,wrap. It also now supports these non-standard attributes:autoSave,results,security.xlinkActuate,xlinkArcrole,xlinkHref,xlinkRole,xlinkShow,xlinkTitle,xlinkType,xmlBase,xmlLang,xmlSpace.imageSVG tag is now supported by React DOM.is="..."attribute).audioandvideotags:onAbort,onCanPlay,onCanPlayThrough,onDurationChange,onEmptied,onEncrypted,onEnded,onError,onLoadedData,onLoadedMetadata,onLoadStart,onPause,onPlay,onPlaying,onProgress,onRateChange,onSeeked,onSeeking,onStalled,onSuspend,onTimeUpdate,onVolumeChange,onWaiting.shallowCompareadd-on has been added as a migration path forPureRenderMixinin ES6 classes.CSSTransitionGroupcan now use custom class names instead of appending-enter-activeor similar to the transition name.New helpful warnings
document.bodydirectly as the container toReactDOM.rendernow gives a warning as doing so can cause problems with browser extensions that modify the DOM.Notable bug fixes
<option>elements with multiple text children properly and renders<select>elements on the server with the correct option selected.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).animationIterationCount,boxOrdinalGroup,flexOrder,tabSize,stopOpacity.Simulate.mouseEnterandSimulate.mouseLeavenow work.React Tools / Babel
Breaking Changes
react-toolspackage andJSXTransformer.jsbrowser file have been deprecated. You can continue using version0.13.3of both, but we no longer support them and recommend migrating to Babel, which has built-in support for React and JSX.New Features
optimisation.react.inlineElementstransform converts JSX elements to object literals like{type: 'div', props: ...}instead of calls toReact.createElement. This should only be enabled in production, since it disables some development warnings/checks.optimisation.react.constantElementstransform hoists element creation to the top level for subtrees that are fully static, which reduces calls toReact.createElementand 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.3Compare Source
React Core
New Features
clipPathelement and attribute for SVGBug Fixes
dangerouslySetInnerHTMLrestrictions so{__html: undefined}will no longer throwgetChildContextreplaceState(obj)retains prototype ofobjReact with Add-ons
Bug Fixes
contextTypesv0.13.2Compare Source
React Core
New Features
strokeDashoffset,flexPositive,flexNegativeto the list of unitless CSS propertiesscoped- for<style>elementshigh,low,optimum- for<meter>elementsunselectable- IE-specific property to prevent user selectionBug Fixes
style={null}didn't properly updatestyleuglifydependency to prevent a bug in IE8React with Add-Ons
Bug Fixes
hasOwnPropertyas an object keyReact Tools
v0.13.1Compare Source
React Core
Bug Fixes
<select>elementsstyleworks when transitioning fromnullReact with Add-Ons
Bug Fixes
getDOMNodefor ES6 classes<html>,<head>,<body>) are treated as DOM componentsReact Tools
Bug Fixes
--non-strict-es6modulev0.13.0Compare Source
React Core
Breaking Changes
propsafter 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 mutatedstatics) are no longer autobound to the component classrefresolution order has changed slightly such that a ref to a component is available immediately after itscomponentDidMountmethod is called; this change should be observable only if your component calls a parent component's callback within yourcomponentDidMount, which is an anti-pattern and should be avoided regardlesssetStatein life-cycle methods are now always batched and therefore asynchronous. Previously the first call on the first mount was synchronous.setStateandforceUpdateon an unmounted component now warns instead of throwing. That avoids a possible race condition with Promises.this._pendingStateandthis._rootNodeID.New Features
React.findDOMNode(component), which should be used in place ofcomponent.getDOMNode(). The base class for ES6-based components will not havegetDOMNode. This change will enable some more patterns moving forward.React.cloneElement(el, props)for making copies of React elements – see the v0.13 RC2 notes for more details.refstyle, allowing a callback to be used in place of a name:<Photo ref={(c) => this._photo = c} />allows you to reference the component withthis._photo(as opposed toref="photo"which givesthis.refs.photo).this.setState()can now take a function as the first argument for transactional state updates, such asthis.setState((state, props) => ({count: state.count + 1}));– this means that you no longer need to usethis._pendingState, which is now gone.Deprecations
ComponentClass.typeis deprecated. Just useComponentClass(usually aselement.type === ComponentClass).createClass-based components are removed or deprecated from ES6 classes (getDOMNode,replaceState,isMounted,setProps,replaceProps).React with Add-Ons
New Features
React.addons.createFragmentwas added for adding keys to entire sets of children.Deprecations
React.addons.classSetis now deprecated. This functionality can be replaced with several freely available modules. classnames is one such module.React.addons.cloneWithPropscan be migrated to useReact.cloneElementinstead – make sure to mergestyleandclassNamemanually if desired.React Tools
Breaking Changes
classmethods are no longer enumerable by default, which requiresObject.defineProperty; if you support browsers such as IE8, you can pass--target es3to mirror the old behaviorNew Features
--targetoption is available on the jsx command, allowing users to specify and ECMAScript version to target.es5is the default.es3restores the previous default behavior. An additional transform is added here to ensure the use of reserved words as properties is safe (egthis.staticwill becomethis['static']for IE8 compatibility).JSXTransformer
Breaking Changes
transformnow containssourceMapas a JS object already, not an instance ofSourceMapGenerator.JSX
Breaking Changes
>or}when inside an element. Previously it would be treated as a string but now it will be treated as a parse error. Thejsx_orphaned_brackets_transformerpackage on npm can be used to find and fix potential issues in your JSX code.v0.12.2Compare Source
React Core
formAction,formEncType,formMethod,formTarget,marginHeight,marginWidthstrokeOpacityto the list of unitless CSS propertiesundefinedtoReact.createElement- now there is a useful warningReact Tools
displayNamev0.12.1Compare Source
React Tools
v0.12.0Compare Source
React Core
Breaking Changes
keyandrefmoved off props object, now accessible on the element directlyReact.__internalsis removed - it was exposed for DevTools which no longer needs accessReact.createFactoryfirst. This is handled for you when using JSX.New Features
{...}) introduced to deprecatethis.transferPropsToacceptCharset,classID,manifestDeprecations
React.renderComponent-->React.renderReact.renderComponentToString-->React.renderToStringReact.renderComponentToStaticMarkup-->React.renderToStaticMarkupReact.isValidComponent-->React.isValidElementReact.PropTypes.component-->React.PropTypes.elementReact.PropTypes.renderable-->React.PropTypes.nodeReact.isValidClassinstance.transferPropsTofalsefrom event handlers to preventDefaultReact.createFactorykey={null}to assign implicit keysBug Fixes
event.getModifierStateas case sensitiveevent.charCodelistupdates correctly nowscrollLeft,scrollTopremoved, these should not be specified as propsReact With Addons
New Features
React.addons.batchedUpdatesadded to API for hooking into update cycleBreaking Changes
React.addons.updateusesassigninstead ofcopyPropertieswhich doeshasOwnPropertychecks. Properties on prototypes will no longer be updated correctly.Bug Fixes
JSX
Breaking Changes
New Features
@jsx React.DOMno longer required{...}) operator introduced to allow easier use of propsBug Fixes
v0.11.2Compare Source
React Core
New Features
<dialog>element and associatedopenattribute<picture>element and associatedmediaandsizesattributesReact.createElementAPI in preparation for React v0.12React.createDescriptorhas been deprecated as a resultJSX
<picture>is now parsed intoReact.DOM.pictureReact Tools
esprimaandjstransformfor correctness fixesjsxexecutable now exposes a--strip-typesflag which can be used to remove TypeScript-like type annotationsrequire('react-tools').transformasstripTypesv0.11.1Compare Source
React Core
Bug Fixes
setStatecan be called insidecomponentWillMountin non-DOM environmentsSyntheticMouseEvent.getEventModifierStatecorrectly renamed togetModifierStategetModifierStatecorrectly returns abooleangetModifierStateis now correctly case sensitiveinnerHTMLworkaround is now removed, fixing rerendering in certain casesJSX
v0.11.0Compare Source
React Core
Breaking Changes
getDefaultProps()is now called once per class and shared across all instancesMyComponent()now returns a descriptor, not an instanceReact.isValidComponentandReact.PropTypes.componentvalidate descriptors, not component instancespropTypevalidators should return anErrorinstead of logging directlyNew Features
nulle.keyande.getModifierState()propertiesonBeforeInputeventReact.Children.counthas been added as a helper for counting the number of childrenBug Fixes
e.viewproperly normalizedcoords,crossOrigin,download,hrefLang,mediaGroup,muted,scrolling,shape,srcSet,start,useMap)classNameon a mounted SVG component now works correctlymaskandtspandx,dy,fillOpacity,fontFamily,fontSize,markerEnd,markerMid,markerStart,opacity,patternContentUnits,patternUnits,preserveAspectRatio,strokeDasharray,strokeOpacityWebkit,ms,Moz,O) are now handled properlyimgevent listeners are now unbound properly, preventing the error "Two valid but unequal nodes with the samedata-reactid"React With Addons
$applycommand to transform valuesReact NPM Module
dist/.envifyis properly listed as a dependency instead of a peer dependencyJSX
<Components.Checkbox />harmonyfeatures available in the command line with<script type="text/jsx;harmony=true">React Tools Module
--harmonyoption--source-map-inlineoption to thejsxexecutabletransformWithDetailsAPI which gives access to the raw sourcemap datav0.10.0Compare Source
React Core
New Features
data-reactid,data-react-checksum). This DOM will not be mountable by React. Read the docs forReact.renderComponentToStaticMarkupsrcSetfor<img>to specify images at different pixel ratiostextAnchorfor SVGBug Fixes
className={false}behaves consistentlythis.refsis defined, even if no refs are specified.Addons
updatefunction to deal with immutable data. Read the docsreact-tools
transformfunction. The only option supported isharmony, which behaves the same asjsx --harmonyon the command line. This uses the ES6 transforms from jstransform.v0.9.0Compare Source
React Core
Breaking Changes
componentDidMountandcomponentDidUpdateno longer receive the root node as a parameter; usethis.getDOMNode()insteadundefined, the default value returned bygetDefaultPropswill now be used insteadReact.unmountAndReleaseReactRootNodewas previously deprecated and has now been removedReact.renderComponentToStringis now synchronous and returns the generated HTML string<html>tag using React) is now supported only when starting with server-rendered markupdeltaYis no longer negatedinput,select, andtextareaelements,.getValue()is no longer supported; use.getDOMNode().valueinsteadthis.contexton components is now reserved for internal use by ReactNew Features
defs,linearGradient,polygon,radialGradient,stopcrossOriginfor CORS requestsdownloadandhrefLangfor<a>tagsmediaGroupandmutedfor<audio>and<video>tagsnoValidateandformNoValidatefor formspropertyfor Open Graph<meta>tagssandbox,seamless, andsrcDocfor<iframe>tagsscopefor screen readersspanfor<colgroup>tagspropTypesin mixinsany,arrayOf,component,oneOfType,renderable,shapetoReact.PropTypesstaticson component spec for static component methods.currentTargetis now properly set.keyis now polyfilled in all browsers for special (non-printable) keys.clipboardDatais now polyfilled in IE.dragTransferis now presentonMouseOverandonMouseOutin addition to the existingonMouseEnterandonMouseLeaveeventsonLoadandonErroron<img>elementsonReseton<form>elementsautoFocusattribute is now polyfilled consistently oninput,select, andtextareaBug Fixes
__owner__property to each component'spropsobject; passed-in props are now never mutatedReact.renderComponentwithincomponentDidMount), events now properly bubble to the parent component.target,.relatedTarget, and.typeare now set properly.datais now properly normalized in IE9 and IE10pxappended for the unitless propertiescolumnCount,flex,flexGrow,flexShrink,lineClamp,order,widowscomponentWillUnmounthandlerrenderComponentToStringwould store event handlersdisabledare rendered without a value (previouslydisabled="true", now simplydisabled)keyvalues containing.are now supporteddata-reactidvalues for performancekeyproperty changesdocumentonly when necessary, improving performance in some cases.returnValuein modern browsers, eliminating a warning in ChromescrollLeftandscrollTopare no longer accessed on document.body, eliminating a warning in ChromeReact with Addons
React.addons.TestUtilswas added to help write unit testsReact.addons.TransitionGroupwas renamed toReact.addons.CSSTransitionGroupReact.addons.TransitionGroupwas added as a more general animation wrapperReact.addons.cloneWithPropswas added for cloning components and modifying their propstransitionLeavein CSSTransitionGroup<input>elements,checkedLinkis now supported for two-way bindingJSX Compiler and react-tools Package
react-toolsnpm package no longer includes the React core libraries; use thereactpackage instead.displayNameis now added in more cases, improving error messages and names in the React Dev ToolsJSXTransformernow uses source maps automatically in modern browsersJSXTransformererror messages now include the filename and problematic line contents when a file fails to parsev0.8.0React
rows&colsfor<textarea>defer&asyncfor<script>loopfor<audio>&<video>autoCorrectfor form fields (a non-standard attribute only supported by mobile WebKit)onContextMenueventsReact with Addons
onTransitionreact-tools
jstransformandesprima-fbJSXTransformer
v0.5.2Compare Source
React
key: CVE-2013-7035v0.5.1Compare Source
React
<input type="range">and selection events.disabledattribute handling on non-<input>elements.React with Addons
v0.5.0React
charSet,content,form,httpEquiv,rowSpan,autoCapitalize).rx,ry).getInitialStateandgetDefaultPropsin mixins.React.version.React.isValidClass- Used to determine if a value is a valid component constructor.React.autoBind- This was deprecated in v0.4 and now properly removed.React.unmountAndReleaseReactRootNodetoReact.unmountComponentAtNode.React with Addons (New!)
JSX
classtoclassNameas part of the transform! This is a breaking change - if you were usingclass, you must change this toclassNameor your components will be visually broken.v0.3.0v0.0.0-experimental-feed8f3f9-20240118Compare Source
v0.0.0-experimental-fdb368d9e-20230725Compare Source
v0.0.0-experimental-fd0da3eef-20240404Compare Source
v0.0.0-experimental-fccf3a9fb-20230213Compare Source
v0.0.0-experimental-fbc9b68d6-20231123Compare Source
v0.0.0-experimental-fb9a90fa48-20240614Compare Source
v0.0.0-experimental-fb10a2c66-20240228Compare Source
v0.0.0-experimental-fa6eab58-20240815Compare Source
v0.0.0-experimental-fa4314841-20230502Compare Source
v0.0.0-experimental-f9ebd85a-20240925Compare Source
v0.0.0-experimental-f994737d14-20240522Compare Source
v0.0.0-experimental-f90a6bcc-20240827Compare Source
v0.0.0-experimental-f828bad38-20230313Compare Source
v0.0.0-experimental-f3e09d6328-20240612Compare Source
v0.0.0-experimental-f38c22b244-20240704Compare Source
v0.0.0-experimental-efb381bbf-20230505Compare Source
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.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR was generated by Mend Renovate. View the repository job log.