This repository was archived by the owner on Dec 26, 2022. It is now read-only.
Update all major dependencies #37
Open
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:
6.4.19->6.5.132.0.6->2.0.716.8->16.180.12.0->0.16.0^0.11.0->^0.14.0Release Notes
storybookjs/storybook
v6.5.13Compare Source
Bug Fixes
v6.5.12Compare Source
Bug Fixes
v6.5.11Compare Source
Bug Fixes
react@18#18737v6.5.10Compare Source
Maintenance
svelte-loaderoptional dependency #18645themes.normalwiththemes.light#17034Bug Fixes
docs.extractArgTypes#18831Dependency Upgrades
v6.5.9Compare Source
Bug Fixes
storyNamein CSF3 exports (#18464)Maintenance
parameters.docsOnlyinstories.json(#18433)v6.5.8Compare Source
Bug Fixes
v6.5.7Compare Source
Bug Fixes
viewModestory (#18370)Maintenance
PreviewWebtests (#18369)v6.5.6Compare Source
Bug Fixes
v6.5.5Compare Source
Bug Fixes
Maintenance
Dependency Upgrades
v6.5.4Compare Source
Bug Fixes
Maintenance
v6.5.3Compare Source
Bug Fixes
v6.5.2Compare Source
Bug Fixes
Dependency Upgrades
v6.5.0Compare Source
Storybook 6.5 is here!! 🎉🎉🎉
SB6.5 adds new testing and design review workflows while improving core performance and compatibility.
More info in the Github issue Storybook 6.5 Release 👟. Release announcement coming soon!!!
v6.4.22Compare Source
Maintenance
v6.4.21Compare Source
Bug Fixes
v6.4.20Compare Source
Bug Fixes
Maintenance
@storybook/builder-vite(#17829)styled-components/babel-plugin-styled-components
v2.0.7Compare Source
What's Changed
New Contributors
Full Changelog: styled-components/babel-plugin-styled-components@v2.0.6...v2.0.7
SonarSource/eslint-plugin-sonarjs
v0.16.0Compare Source
What's Changed
no-redundant-boolean): Improve message by @victor-diez-sonarsource in https://github.com/SonarSource/eslint-plugin-sonarjs/pull/369Full Changelog: SonarSource/eslint-plugin-sonarjs@0.15.0...0.16.0
v0.15.0Compare Source
v0.14.0Compare Source
no-gratuitous-expressions: inlined react expression@babel/eslint-parserv0.13.0Compare Source
New suggestions
Many thanks to our contributor! 🥇
Full Changelog: SonarSource/eslint-plugin-sonarjs@0.12.0...0.13.0
facebook/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.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.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
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.
This PR has been generated by Mend Renovate. View repository job log here.