Phew what an exciting few days it has been! We've been blown away by the wonderful responses to our 10.0.0-alpha.0
release and are excited to ship the next one with a good dozen of bug fixes.
In just three days we received a lot of awesome PRs pushing Preact X forward 👍 This wouldn't be possible with the outstanding issues we've received. They all had a link to a codesandbox where the issue could be easily reproduced. This is every maintainer's dream and we can't stress enough how much time it saves us to fix bugs 🚀
- Switch away from
MessageChannel
tosetTimeout + requestAnimationFrame
🎉 (#1346, thanks @cristianbote) - Fix lifecycle order of
componentWillReceiveProps
in relation toshouldComponentUpdate
💯(#1348, thanks @mochiya98) - Fix incorrect operator precedence in
memo()
🎉 (#1347, thanks again @mochiya98) - Preserve devtools global hook 🔧 (#1333, thanks @developit)
- Fix missing
server.js
in npm package (#1332, thanks @developit) - Fix incorrect
this
binding insetState
callback (#1344, thanks @marvinhagemeister) - Fix stale
props
andstate
reference whenshouldComponentUpdate
returnsfalse
(#1351, thanks @marvinhagemeister) - Don't leak
Text
nodes out oftoChildArray
(#1357, thanks @developit) - Add missing consistent mangle name for
_parentDOM
(#1320, thanks @andrewiggins) - Add
hgroup
to TypeScript typings (#1340, thanks @ForsakenHarmony) - Add missing
isReactComponent
-property inpreact/compat
(#1337, thanks @marvinhagemeister) - Downgrade IE11 to run on Windows 7 in Saucelabs (#1319, thanks @marvinhagemeister)