Releases: single-spa/single-spa-angular
Releases · single-spa/single-spa-angular
v3.0.0-rc.1
v3.0.0-beta.26
Fixes
- Fixed bug where links between applications threw error. (joeldenning/coexisting-angular-microfrontends#3, f998ab4)
v3.0.0-rc.0
Release candidate
Version 3 includes support for angular-cli and works with Angular 2-8.
v3.0.0-beta.27
Features
- Support for angular 8, via @angular-builders/custom-webpack. Angular 7 and below will continue using single-spa-angular builder (#83)
v3.0.0-beta.25
v3.0.0-beta.24
v3.0.0-beta.22
v3.0.0-beta.21
v3.0.0-beta.20
Fixes
- Removed some (but not all 😢) of the
Navigation triggered outside of Angular zone
warnings (#69 from @jlewicki-nevo) - Improved support for using Angular's
--project
feature (#68 from kbjerke)
v3.0.0-beta.19
Features
- Lazy loading is now possible via SystemJS (fe37476)
- You can now put your html file into a separate git repo and directory, which doesn't have to be a parent directory of your applications.
- Users are encouraged to use single-spa-playground.org to set up their single spa application (fe37476)
Fixes
Migrating from 3.0.0-beta.17
Update your main.single-spa.ts
file to no longer export default
. Instead, it should do the following:
const lifecycles = singleSpaAngular({...})
export const bootstrap = lifecycles.bootstrap
export const mount = lifecycles.mount
export const unmount = lifecycles.mount
Now go to single-spa-playground.org and follow the instructions there.