@angular-architects/native-federation 19.0.14 → 19.0.15

package/README.md

@@ -336,15 +336,15 @@ Now, by clicking at the 2nd menu item, you can load the remote directly into the
 
 ## Advanced Use Cases
 
-## SSR and Hydration
+### SSR and Hydration
 
 We support Angular's SSR and (Incremental) Hydration. Please find [more information here](https://www.angulararchitects.io/blog/ssr-and-hydration-with-native-federation-for-angular/).
 
-## Native Federation and Module Federation
+### Native Federation and Module Federation
 
 We support combining Native Federation with Module Federation. Please find [more information here](https://www.angulararchitects.io/blog/combining-native-federation-and-module-federation/).
 
-## Angular I18N
+### Angular I18N
 
 Since version 19.0.13, Native Federation for Angular supports Angular I18N. Here are some things to keep in mind:
 
@@ -352,7 +352,7 @@ Since version 19.0.13, Native Federation for Angular supports Angular I18N. Here
 - Configure I18N in your `angular.json`. Don’t use command line parameters (as the Native Federation Builder does not forward them to the ApplicationBuilder by design)
 - In production, make sure your `federation.manifest.json` points to the right language versions of your remotes
 
-## Angular Localization
+### Angular Localization
 
 To just build the localization files you need for federation, you can use the `shareAngularLocales` introduced with version 19.0.14:
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@angular-architects/native-federation",
-  "version": "19.0.14",
+  "version": "19.0.15",
   "main": "src/index.js",
   "generators": "./collection.json",
   "builders": "./builders.json",