Releases: preactjs/preact
Releases · preactjs/preact
4.1.2
This is purely a bug fix release, so be sure to update if you're using Preact 4.x.
Bugs Fixed:
- Fix orphaned keyed VNodes not being removed in certain cases, such as when there are adjacent non-orphaned non-keyed VNodes (see preactjs/preact-compat#21)
- When diffing a component against a non-component VNode, if the component render returns a different DOM node, make sure to reclaim the original node. (Issue #73)
4.1.1
4.1.0
4.0.1
- Cancel preliminary support for String
refs
. Preact core will only be supporting function refs, since String refs are "mostly" deprecated.
4.0.0
- Add support for
refs
! - Add support for
defaultProps
(static property on Components) - Possibly Breaking Change: cache rendered DOM with components when recycling
- Possibly Breaking Change: don't wipe recycled DOM nodes, simply diff when re-used
- Use
setImmediate()
to improvesetState()
performance where available - Skip empty values when serializing
style
objects - Coerce falsey
className
andstyle
values to an empty string to avoidclass="null"
andstyle="null"
- Rename missing component insert from
<x-undefined-element>
to<undefined>
- Use a
Symbol
for storing the prop cache where available
3.4.0
3.3.0
- Performance tuning for a ~10% improvement on DBMonster (basically 10% faster diff algorithm)
- Refactored diff algorithm to be easier to follow
- Add
Component.prototype.forceUpdate()
method. - Fix a bug where a child component of a high-order component self-rendering (eg: via
setState()
) would cause a subsequent re-render of the parent component to re-initialize itself and the child (through the recycler, but this was causing thrash). - Fix an issue where nested components would not receive unmount lifecycle hooks (fixes Issue #47)
3.2.0
- Bugfix: pass
context
through recycled constructors (with thisreact-redux
is now fully supported!) linkState()
when used with top-level keys (ie, not dot-notated) will no longer mutatethis.state
in-place.(Nested keys can and will still mutate this.state, since the implementation of immutable state traversal would essentially be a small immutability library, not something Preact core can justify)
3.1.0
3.0.1
This is likely the last beta release of Preact 3.0, it'll become the stable branch shortly.
Feedback and testing welcome!
- Use a safeguard method to obtain preact attr cache objects before writes
- Fix edge case where fallthrough attribute values would not be stored in the preact attr cache
null
instead ofdelete
for_component
refs, avoiding shape mutations- build tweaks