Releases: single-spa/single-spa-angular
Releases · single-spa/single-spa-angular
v2.2.1
Fixes
- Fixed bug where bootstrap lifecycle threw an error. This was a regression introduced in v2.2.0 (eda495f and joeldenning/simple-single-spa-webpack-example#20)
v3.0.0-beta.17
v3.0.0-beta.15
v3.0.0-beta.14
v3.0.0-beta.13
Fixes
Features
- single-spa-angular now defaults to using Angular routing. (#50)
- ApplicationRef is no longer required to be passed into single-spa-angular as an opt. (d991598). This requires using [email protected], which has this fix for routing. Also see #49 as a related issue.
v3.0.0-beta.12
Features
- Multiple Angular apps can be active at the same time without ZoneJS errors (!!) (e5a94f4, #47, PlaceMe-SAS/single-spa-angular-cli#33)
domElementGetter
is no longer required -- a default implementation now will cover most use cases. (e5a94f4)
v3.0.0-beta.11
Fixes
Features
- A partial webpack config is now supported for both
ng build
andng serve
. (#40 via @pauljmelia)
v2.2.0
Fixes
- Multiple angular apps can be active without ZoneJS errors, when you provide the NgZone opt. (696720f, #47, and PlaceMe-SAS/single-spa-angular-cli#33)
Example usage in 2.x branch Readme
Note that this fix is also in the master branch and part of single-spa-angular@>=3
v3.0.0-beta.10
Breaking changes
- The single-spa-angular opts saw significant changes. The
mainModule
andplatform
opts no longer exist. Instead, there is a new opt calledbootstrapFunction
that is required. See this documentation for more info on how to use the new API. This breaking change was necessary in order to implement the features and fixes in this release (#43)
Features
ng build --prod
bundle size on a new angular-cli app is cut in half (about 250kb reduction) (#43)
Fixes
Lazy routes discovery not enabled
warning is gone fromng build
(#43)
v3.0.0-beta.9
Fixes
ng serve
should now work on Windows (tested and verified) (667b44b)