This version is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of preact.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
7dad020Tweak opinionated optimization of component recycling: recursively break down trees by default since performance seems better.
8a1b5acAvoid key lookup if there are no children to be compared with
cf855a9Fix possible issue when re-rendering an element with a style object that was previously rendered using a style string.
5be48c7Drop memoize(), since it's now only used for toLowerCase() and can be simply inlined.
a5b286bBOOM 🎇 Style objects now have a lightning fast pipeline out to the DOM. Fixes #228! (+ more tests to cover switching between various style types)
21ae8c8Inline single-use getKey() in such a way that it doesn't deopt the rest of the diff.
92d5449Inline an unnecessarily factored out diff method to reduce stack depth
bd3b6f0Size & performance optimizations for isSameNodeType().
515dac5When recycling components, move base to nextBase to prevent later incorrectly treating components as already-mounted upon reuse. /cc @kruczy @madumo
0fc99d2Add a few more permutations of lifecycle tests
cbc2e9fSpecial-case nulling of ref for component bases so it happens between componentWillUnmount and componentDidUnmount (+test case from @slmgc!). Fixes #232.
Hello lovely humans,
preact just published its new version 5.3.0.
This version is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of preact. Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right? Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project :sparkles:
You rock!
:palm_tree:
The new version differs by 307 commits .
eede3a8
5.3.0
7dad020
Tweak opinionated optimization of component recycling: recursively break down trees by default since performance seems better.
8a1b5ac
Avoid key lookup if there are no children to be compared with
cf855a9
Fix possible issue when re-rendering an element with a style object that was previously rendered using a style string.
5be48c7
Drop
memoize()
, since it's now only used fortoLowerCase()
and can be simply inlined.a5b286b
BOOM 🎇 Style objects now have a lightning fast pipeline out to the DOM. Fixes #228! (+ more tests to cover switching between various style types)
21ae8c8
Inline single-use
getKey()
in such a way that it doesn't deopt the rest of the diff.92d5449
Inline an unnecessarily factored out diff method to reduce stack depth
bd3b6f0
Size & performance optimizations for
isSameNodeType()
.515dac5
When recycling components, move
base
tonextBase
to prevent later incorrectly treating components as already-mounted upon reuse. /cc @kruczy @madumo0fc99d2
Add a few more permutations of lifecycle tests
1f21c3b
Tiny size optimization to offset #232.
cbc2e9f
Special-case nulling of
ref
for component bases so it happens betweencomponentWillUnmount
andcomponentDidUnmount
(+test case from @slmgc!). Fixes #232.bd405f5
Merge branch 'slmgc-master'
11df12f
Fix
ref
becoming null beforecomponentWillUnmount
.There are 250 commits in total. See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? :zap:
greenkeeper upgrade