You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
-`sharedMappings` is optional. If you omit it, all mapped paths are shared.
39
+
- You can use wildcard suffixes (for example, `@my-org/ui/*`) to include multiple mapped paths.
40
+
-`skip` still applies and can be used to exclude mapped paths even if they were selected via `sharedMappings`.
41
+
- Mapped paths are read from the workspace root tsconfig file: `tsconfig.base.json` if present, otherwise `tsconfig.json`.
42
+
- The workspace root is detected by searching upward from the current working directory until a `package.json` is found.
43
+
44
+
## Mapping Versions via `features.mappingVersion`
45
+
46
+
If your mapped paths point to libraries that have a `package.json` with a `version`, you can include this version in federation metadata by enabling `features.mappingVersion`.
- If enabled, Native Federation tries to read the version from the mapped library's nearest `package.json`.
68
+
- If no `package.json` version is found for a mapping, the version remains empty.
69
+
17
70
## Using Multiple Framework Versions
18
71
19
72
After compiling an Angular application, the compilation is accessing Angular's private API. As private APIs do not align with semver, there is no guarantee that your compiled application works with a different version of Angular. Even having a different minor or patch version at runtime can lead to issues.
0 commit comments