@module-federation/nextjs-mf 5.1.3 → 5.2.0
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 +2 -0
- package/lib/NextFederationPlugin.js +3 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -134,6 +134,7 @@ new NextFederationPlugin({
|
|
|
134
134
|
exposePages: true, // `false` by default
|
|
135
135
|
enableImageLoaderFix: true, // `false` by default
|
|
136
136
|
enableUrlLoaderFix: true, // `false` by default
|
|
137
|
+
skipSharingNextInternals: true // `false` by default
|
|
137
138
|
},
|
|
138
139
|
});
|
|
139
140
|
```
|
|
@@ -141,6 +142,7 @@ new NextFederationPlugin({
|
|
|
141
142
|
- `exposePages` – exposes automatically all nextjs pages for you and theirs `./pages-map`.
|
|
142
143
|
- `enableImageLoaderFix` – adds public hostname to all assets bundled by `nextjs-image-loader`. So if you serve remoteEntry from `http://example.com` then all bundled assets will get this hostname in runtime. It's something like Base URL in HTML but for federated modules.
|
|
143
144
|
- `enableUrlLoaderFix` – adds public hostname to all assets bundled by `url-loader`.
|
|
145
|
+
- `skipSharingNextInternals` - skips sharing of common nextjs modules. Helpful when you would like explicit control over shared modules, such as a non-nextjs host with a federated nextjs child application.
|
|
144
146
|
|
|
145
147
|
## Demo
|
|
146
148
|
|