📦 Update dependency preact to v10.5.13#34241
Closed
renovate-bot wants to merge 1 commit intoampproject:mainfrom
Closed
📦 Update dependency preact to v10.5.13#34241renovate-bot wants to merge 1 commit intoampproject:mainfrom
renovate-bot wants to merge 1 commit intoampproject:mainfrom
Conversation
Contributor
|
This needs accompanying fixes. They were being done via #30043 for an older version of Preact. |
This file contains hidden or 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
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:
10.2.1->10.5.13How to resolve breaking changes
This PR may introduce breaking changes that require manual intervention. In such cases, you will need to check out this branch, fix the cause of the breakage, and commit the fix to ensure a green CI build. To check out and update this PR, follow the steps below:
Release Notes
preactjs/preact
v10.5.13Compare Source
Bug Fixes
tabIndex(#3062 + #3064, thanks @marvinhagemeister)compat/server(#3059 + #3061, thanks @marvinhagemeister)bigintnumbers (#3010, thanks @marvinhagemeister)Types
decodingattribute (#3054, thanks @sumanthratna)SVGFEFunctypes (#3043, thanks @rschristian)Maintenance
options.unmountinstead of overridingcomponent.componentWillUnmount(#2919, thanks @tanhauhau)v10.5.12Compare Source
This release includes an enhancement to our devtools integration. Via a babel plugin you can get more readable hook names to show up in devtools instead of dozens of
useStatehooks in devtools. Check out https://github.com/preactjs/babel-plugin-transform-hook-names for more information.Before:
After:
Bug Fixes
defaultValuenot applied when value==null/undefined(#2957, thanks @marvinhagemeister)Maintenance
console.logs(#2959, thanks @marvinhagemeister)v10.5.11Compare Source
📈 Bug Fixes
contentEditabletofalse(#2938, #2939 thanks @marvinhagemeister + @developit)compat/jsx-dev-runtimemissing in package (#2931, thanks @marvinhagemeister)⛳ Code golfing
createElementinstead of justis[-5b] (#2943, thanks @developit)xlink:(#2939, thanks @developit)🛠️ Maintenance
reacttopreact/compat(#2946, thanks @marvinhagemeister)workflow_dispatchand restructure branch trigger (#2933, thanks @andrewiggins)v10.5.10Compare Source
Bug Fixes
contentEditablethrowing when set to undefined/null (#2927, thanks @marvinhagemeister)jsx-dev-runtimepackage entry (#2920, thanks @sventschui)Suspense(#2917, thanks @andrewiggins)Maintenance
Portaltest not cleaning up container (#2925, thanks @marvinhagemeister)sinondependencies to fix IE11 Promise error (#2922, thanks @marvinhagemeister)karmabenchmarks not compiling (#2914, thanks @marvinhagemeister)babel-loader(#2911, thanks @andrewiggins)v10.5.9Compare Source
Happy New Year to everyone 🎉 Let's kick of the year with a few welcome bug fixes regarding
preact/compat👍Bug Fixes
memo(#2896, thanks @andrewiggins)Maintenance
v10.5.8Compare Source
This is probably the last release for 2020. Thank you everyone for the amazing contributions over the year and we can't wait to see where Preact is going in 2021! Lot's of interesting ideas are being worked on 🎉
Bug Fixes
_nextDompointer if it is being unmounted (#2889, thanks @andrewiggins)/compat/serverexports to work with import/export syntax and webpack 5 (#2873, thanks @SomethingSexy)useMemo/useCallbackhooks (#2870, thanks @afzalsayed96)VNodetype (#2855, thanks @andrewiggins)refnot being removed frompropswithjsx-runtime(#2840, thanks @marvinhagemeister)onchangetooninputforinput[type=range]in IE11 (#2817, thanks @gcraftyg)Types
JSDoccomments (#2883, thanks @andrewiggins)CSSStyleDeclarationfor CSS property list (#2869, thanks @developit)readonlyattribute (#2868, thanks @rschristian)defaultValuefor select tag (#2848, thanks @Rafi993)_originaltypings (#2830, thanks @marvinhagemeister)csstypefrom version 2 to version 3 (#2829, thanks @bz2)Other
vnodere-use detection (-2 B) (#2863, thanks @marvinhagemeister)diffChildren(#2813, thanks @JoviDeCroock)Maintenance
createRootAPI (#2866, thanks @andrewiggins)FUNDING.yml(#2861, thanks @JoviDeCroock)devDependencies(#2856, thanks @andrewiggins)v10.5.7Compare Source
compat/jsx-runtimemissing in npm package (#2827, thanks @marvinhagemeister)v10.5.6Compare Source
Bug Fixes
jsx-runtimework when using an alias (#2805, thanks @JoviDeCroock)Types
animateTransformtag type (#2822, thanks @HuHguZ)displayNameto context (#2820, thanks @max-voronov)styleattribute types (#1797, thanks @mnkhouri)jsx-runtime, fixes TS4.1 compatibility (#2811, thanks @ddprrt)reftypes' current property non-optional (#2803, thanks @ivantm)Maintenance
vnodereference and golf implementation (#2517, thanks @JoviDeCroock)v10.5.5Compare Source
Bug Fixes
Suspensetriggers (#2796, thanks @JoviDeCroock)Typings
v10.5.4Compare Source
tl;dr: Bug-Fix only release that should get rid of the last className edge cases. We encourage everyone to upgrade.
Despite our effort to account for all edge cases regarding
classNamehandling inpreact/compat, we got some reports of some missed ones. This release corrects those 🎉This release contains a fix to increase compatibility with next.js that ensures that the error overlay will show up.
Bug Fixes
classNamedescriptors on Elementvnodes(#2786, thanks @developit)classNameoverclass(#2782, thanks @JoviDeCroock)v10.5.3Compare Source
This release fixes a regression in regards to
class/classNamehandling inpreact/compat. We encourage everyone to upgrade.Bug Fixes
classNamenormalization (#2774, thanks @JoviDeCroock)Promisesin Suspense (#2776, thanks @kitten)Maintenance
check-export-map(#2777, thanks @marvinhagemeister)v10.5.2Compare Source
jsx-runtime(#2769, thanks @marvinhagemeister)v10.5.1Compare Source
jsx-runtimepackage (#2767, thanks @johakr)v10.5.0Compare Source
New JSX-runtime functions
This has been a long time in the making for various virtual-dom based frameworks. Historically JSX was always transpiled to
createElementfunction calls.While this has served us well and is very reliable, it has proven to be hard to optimize. Most of the things we do in our
createElementfunction could by done by babel directly, thereby making it smaller and faster. This is very desirable for us as this function is called a lot in any application. It's part of the so-called hot-path.And that's exactly what the new signature does. It removes the need for us to pull out key from
props, add backchildrento props and just makes the implementation simpler. As a nice benefit users won't need to manually importh/createElementanymore 🎉Usage with babel:
Note that the JSX transformer in TypeScript is a work in progress and will likely be released as part of version 4.1. We're currently running into microsoft/TypeScript#40502 though, so the JSX typings are not found.
Features
jsx-runtimesupport (#2764, thanks @JoviDeCroock, @marvinhagemeister)Bug Fixes
0(#2757, thanks @marvinhagemeister)contenteditable(#2701, thanks @sventschui)style(#2723, thanks @JoviDeCroock)Maintenance
_suspended(#2765, thanks @marvinhagemeister)v10.4.8Compare Source
tl;dr: A good handful of bug fixes make this release the ideal candidate to upgrade! Should be very safe to upgrade
Thanks to all the people who made this release possible! This is for everyone who took part in our discussions, helped report issues, did code contributions or just spread the word. Thank you all for another amazing release 🙌
Golfing
Bug Fixes
readonlyin update fn (#2717, thanks @marvinhagemeister)preact/debug(#2711, thanks @marvinhagemeister)undefinedinstead ofnullinpreact/compat(#2695, thanks @aralroca)react-relay(#2692, thanks @marvinhagemeister)hrefon nullish value (#2693, thanks @marvinhagemeister)undefinedas default value foruseRef(#2689, thanks @marvinhagemeister)preact/debug: Add component stack to prop type validation error, do not pass ref to prop-types validation (fixes mui incompatbility) (#2685, thanks @sventschui)Typings
domlib (#2713, thanks @Gerrit0)useDebugValuetypings to align with React (#2699, thanks @leader22)useErrorBoundarycompat types (#2631, thanks @38elements)IntrinsicElementsinComponentProps(#2680, thanks @remcohaszing)Maintenance
CONTRIBUTING.md(#2702, thanks @marvinhagemeister)v10.4.7Compare Source
tl;dr: This is a bug-fix only release and safe to upgrade 🎉
This release contains some amazing fixes by first time contributors! Thank you so much for everyone who filed issues or contributed PRs ❤️
Bug Fixes
downloadattribute handling (#2674, thanks @marvinhagemeister)diffElementNodes(#2658, thanks @perseveringman)useReftonull(#2648, thanks @JoviDeCroock)setStateinconstructor(#2640, thanks @sventschui)Types
useRefto optional (#2651, thanks @38elements)capturedefinition. (#2643, thanks @JonathanBristow)preact/compattypes (#2628, thanks @jeremy-coleman)Maintenance
package.json"authors" field (#2635, thanks @developit)v10.4.6Compare Source
tl;dr: This is a bug-fix only release and safe to upgrade 🎉
We've landed some very anticipated fixes and therefore thought to cut a new release not soon after 🙌
Bug Fixes
childrenif they'renullin suspense (#2570, thanks @sventschui)textareadoesn't reset state (#2615, thanks @JoviDeCroock)nulltoforwardRef(#2600, thanks @JoviDeCroock)Typings
strokeMiterlimitaccept a number as well (#2620, thanks @lfamorim)feDropShadowdefinition (#2609, thanks @Somnid)Maintenance
LICENSEfiles and fix submodule names (#2611, thanks @hbroer)CONTRIBUTING.md(#2603, thanks @futantan)v10.4.5Compare Source
This is a bugfix-only release and updating is seamless. We encourage everyone to do so 👍
Bug Fixes
Suspensefrom inadvertently modifying sharedComponentclass (#2594, thanks @andrewiggins)Fragmentedge case (#2551, thanks @JoviDeCroock)requestAnimationFramewhile cancelling effects it (#2573, thanks @Hydrophobefireman)setStatein render (#2565, thanks @jamesb3ll)forwardRefpassing object instead of null (#2567, thanks @marvinhagemeister)compat(#2558, thanks @btk5h)useReducerfrom mutating the previous returned result (#2550, thanks @JoviDeCroock)Maintenance
v10.4.4Compare Source
This is a hotfix for today's 10.4.2 release that:
v10.4.3Compare Source
v10.4.2Compare Source
What a month we had! The weather is getting warmer and I think we can all enjoy a new refreshment in the form of a Preact release! The past weeks saw a good chunk of bug fixes and a bit of house keeping. Upgrades should be as straightforward as swapping out the version number in
package.jsonand runningnpm installoryarn installonce!Introducing prefresh (experimental)
It was one of those miracle days where all the pieces fell into place just perfectly: @JoviDeCroock got a HMR (=hot module reloading) prototype up without any changes to Preact and running in a couple hours! With the biggset achievement being that it works amazingly well in keeping hooks state around.
Since then he was contacted by various maintainers of bundlers to collaborate on an ideal developer experience. Today, about a little more than a week later we have them ready to be tested. And we need your feedback to make it the best HMR experience we can! Please file any issue you come across!
Snowpack template
Oh and while we were at it @sventschui added a Preact template for snowpack! You can get it up and running via this line:
Preact sightings
Recently deno cut it's 1.0.0 release which is a huge achievement. It's a new spin on what node could look like if it would have started fresh in 2019 and we're excited where this experiment will lead to! Despite it being very early it made some waves in our community and we were filled with joy when we noticed that the website is built with our beloved framework!
Bug Fixes
React.StrictModetocompat(#2529, thanks @developit)useReducer(#2526, thanks @hadeeb)IS_NON_DIMENSIONALfor compatibility with animation-iteration-count (#2523, thanks @viko16)debug(#2514, thanks @JoviDeCroock)hydrateexport incompat(#2511, thanks @hadeeb)useEffect(#2493, thanks @JoviDeCroock)Types
StrictModetocompat/src/index.d.ts(#2530, thanks @38elements)loadingattribute toHTMLAttributesTypeScript interface (#2521, thanks @gerardo-rodriguez)Maintenance
CONTRIBUTING.mdindentation (#2528, thanks @Vincent-Carrier)spyhelper (#2524, thanks @JoviDeCroock)Fragments(#2507, thanks @andrewiggins)processingExceptioncheck (#2483, thanks @JoviDeCroock)excessDomChildrencreation (#2491, thanks @andrewiggins)js-framework-benchmark(#2489, thanks @andrewiggins)v10.4.1Compare Source
tl;dr: This release allows our devtools extension to inspect hooks. Apart from that it includes the usual round of bug fixes.
We have a nice little present for you and that is hooks are now fully supported in Preact Devtools 0.5.0 🎉 The extension is currently awaiting approval in browsers stores and your browser will automatically update to it in the following days.
Both @andrewiggins and @JoviDeCroock went full on bug hunting mode and got some neat fixes in! We also saw an awesome contribution from @davidje13 who found an error in our types for
memo👍But the true star from the show is without a doubt that we finally have updated our typings to bring back the
marqueeelement. @developit himself took the honors and made sure that developers can continue to use this element in their demo applications.Bug Fixes
setPropertyto set "value" and "checked" properties (#2472, thanks @andrewiggins)cloneElement(#2469, thanks @JoviDeCroock)displayName(#2454, thanks @marvinhagemeister)Typings
<marquee>typings (#2466, thanks @developit)defaultPropswhen wrapping components withmemo(#2461, thanks @davidje13)Maintenance
v10.4.0Compare Source
tl;dr: This release contains some very amazing improvements to hydration and to performance when memoized
vnodesare used. We recommend everyone to upgrade 🎉We understand that the past weeks have been very strange for everybody across the world. We've spent that last weeks mainly focusing on making sure our families and loved ones are safe and taken care of. Whether you're using Preact at work or in a sideproject we hope that this release brings you a little bit of joy and makes your day a little bit brighter 🌠
Strictly equal
vnodesbail out of renderWhen an
vnodeis equal to the one from the last render we will successfully bail out of rendering. This is a performance optimization many state libraries frequently make use of. The most well known of those is probablyreact-redux. We've wanted to add this for the initial Preact X release but had to postpone due to not having found the proper solution back then. In the following months we've passed around various ideas on how to best solve this and it wasn't until last month when it finally clicked and the pieces fell together. @JoviDeCroock had a prototype up running in a few days and has spent a lot of time into making sure that this performance optimization works in all scenarios. We can't stress enough how much of an accomplishment this is. This is really amazing work by @JoviDeCroock and we're over the moon that it has finally landed in Preact 🎉hydrate falls back to render for new subtrees
When doing SSR there are cases where the DOM tree and the
vnodesdon't match. This can lead to a lot of problems, but for now we handle situations a bit more gracefully when there is no existing DOM node present. If we encounter that, we just opt out of hydration for that tree and revert back to doing a full diff. In the future we plan to add more warnings topreact/debugfor that.Features
vnodes(#2386, thanks @JoviDeCroock)hydration(#2438, thanks @JoviDeCroock)Bug Fixes
setPropertyfor known bypass cases (key, children) (#2213, thanks @developit)actcallback (#2433, thanks @robertknight)refis mutable even if a DOM node is inserted into it (#2422, thanks @JoviDeCroock)defaultValue(#2420, thanks @JoviDeCroock)Typings
acttype signature (#2444, thanks @ddayguerrero)_patchedLifecyclestocompat/src/internal.d.ts(#2408, thanks @38elements)Maintenance
typeof(#2409, thanks @polemius)v10.3.4Compare Source
This is a maintenance release, upgrading should be free, please do report it in case you encounter any issues.
render-queue sorting
Preact batches all rendering work and executes from the top of the Virtual DOM tree to the bottom. However, if new rendering tasks were added during an existing render, they were processed without regard for their depth in the tree.
Thanks to a clever fix from @jviide, Preact's render queue is now immutable. Any new tasks added during rendering are placed into a second batch.
material-ui integration
A peculiar issue users were seeing with material-ui related to a ref never getting populated, we went very deep into the codebase and found out that our forwardRef was a bit too eager, at creation it would already start forwarding. We moved this to a later point, now just before the vnode will get diffed the ref will be forwarded.
Fixes:
Maintenance:
Configuration
📅 Schedule: "after 12am every weekday" in timezone America/Los_Angeles.
🚦 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 this update again.
This PR has been generated by WhiteSource Renovate. View repository job log here.