@angular-architects/native-federation 16.1.0 → 16.1.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +8 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -53,6 +53,8 @@ Start the Micro Frontend:
|
|
|
53
53
|
ng serve mfe1 -o
|
|
54
54
|
```
|
|
55
55
|
|
|
56
|
+
_(In the case of an error, see this [information below](#error-file-srcmaints-is-missing-from-the-typescript-compilation-plugin-angular-compiler"))_
|
|
57
|
+
|
|
56
58
|
Wait until the Micro Frontend is started.
|
|
57
59
|
|
|
58
60
|
Open another console and start the shell:
|
|
@@ -278,6 +280,8 @@ Start the remote:
|
|
|
278
280
|
ng serve mfe1 -o
|
|
279
281
|
```
|
|
280
282
|
|
|
283
|
+
_(In the case of an error, see this [information below](#error-file-srcmaints-is-missing-from-the-typescript-compilation-plugin-angular-compiler"))_
|
|
284
|
+
|
|
281
285
|
Once the remote is started, start the shell:
|
|
282
286
|
|
|
283
287
|
```
|
|
@@ -292,6 +296,10 @@ Now, by clicking at the 2nd menu item, you can load the remote directly into the
|
|
|
292
296
|
|
|
293
297
|
If you like the idea of webpack Module Federation but want to switch over to Angular's new esbuild builder (currently in developer preview), you can use this package.
|
|
294
298
|
|
|
299
|
+
### Error: File 'src\main.ts' is missing from the TypeScript compilation. [plugin angular-compiler]
|
|
300
|
+
|
|
301
|
+
It seems like the current version of Angular's esbuild builder has an issue with paths on Windows when using the traditional command prompt. For the time being, try to ng serve and ng build your application via PowerShell, the git bash, or WSL.
|
|
302
|
+
|
|
295
303
|
### I get an error when preparing shared packages. What to do?
|
|
296
304
|
|
|
297
305
|
Native Federation needs to prepare all your shared packages so that it can load them on demand as EcmaScript modules. This only happens once for development and once for production builds. The result of this is cached.
|