v4.5.0

Maintenance

• Use browserslist-config-single-spa and dom-element-getter-helpers. This should not be a breaking change but we're unsure if we missed something that could cause breakage, so we are first publishing this as a beta. npm install --save single-spa-react@beta (#127)
• Skip unnecessary CI/CD builds (#128)

v4.5.0-beta.0

Maintenance

• Use browserslist-config-single-spa and dom-element-getter-helpers. This should not be a breaking change but we're unsure if we missed something that could cause breakage, so we are first publishing this as a beta. npm install --save single-spa-react@beta (#127)
• Skip unnecessary CI/CD builds (#128)

v4.4.0

Features

• When using <Parcel> component, the domElement prop is now passed to parcels that are being updated. This is helpful for them to ensure that the parcel updates the correct dom element rather than creating a new dom element. (#126)

Fixes

• Fix issue where parcels created by single-spa-react weren't properly updated if they used ReactDOM.render() rather than ReactDOM.createRoot().render(). This fixes things for React < 18 (#126)

v4.3.1

Fixes

• types: add props to loadRootComponent (#122 via @scarabedore)

v4.3.0

Features

• Support for passing errorBoundary and errorBoundaryClass as single-spa props (in addition to being able to do so via singleSpaReact(opts) opts object). (#120 - Documentation)

v4.2.1

Fixes

• Fix update lifecycle. Resolves #117. #118

v4.2.0

Features

• Support for React 18. This was a somewhat significant refactor, with no intended changes to functionality. If you find any differences when upgrading to [email protected], please file a github issue. (#114, #112)

v4.1.2

Fixes

• Avoid bundling single-spa-react into Parcel component. See #105. (#111)

v4.1.1

Fixes

• Fixed using mountParcel from React context when rendering <Parcel> inside of a single-spa application (#106 #105)

v4.1.0

Features

• Type definitions for SingleSpaContext are now exposed. (#104 via @ngfk)