@module-federation/nextjs-mf 5.1.2 → 5.1.3
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 +3 -1
- package/lib/loaders/helpers.js +2 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -5,7 +5,7 @@ This plugin enables Module Federation on Next.js
|
|
|
5
5
|
### Supports
|
|
6
6
|
|
|
7
7
|
- next ^11.x.x || ^12.x.x
|
|
8
|
-
- Client side only, SSR
|
|
8
|
+
- Client side only, SSR has a PR open. Help needed
|
|
9
9
|
|
|
10
10
|
I highly recommend referencing this application which takes advantage of the best capabilities:
|
|
11
11
|
https://github.com/module-federation/module-federation-examples
|
|
@@ -16,6 +16,8 @@ SSR support for federated applications is much harder, as such - it utilizes a d
|
|
|
16
16
|
If you need SSR support, consider this package instead - it does everything that nextjs-mf does, and them some.
|
|
17
17
|
https://app.privjs.com/buy/packageDetail?pkg=@module-federation/nextjs-ssr
|
|
18
18
|
|
|
19
|
+
There is a pull request moving SSR into this repo and package - but it is not ready yet.
|
|
20
|
+
|
|
19
21
|
## Whats shared by default?
|
|
20
22
|
|
|
21
23
|
Under the hood we share some next internals automatically
|
package/lib/loaders/helpers.js
CHANGED
|
@@ -23,9 +23,10 @@ module.exports.hasLoader = function hasLoader(rule, loaderName) {
|
|
|
23
23
|
const loader = rule.use[i];
|
|
24
24
|
// check exact name, eg "url-loader" or its path "node_modules/url-loader/dist/cjs.js"
|
|
25
25
|
if (
|
|
26
|
+
loader.loader && (
|
|
26
27
|
loader.loader === loaderName ||
|
|
27
28
|
loader.loader.includes(`/${loaderName}/`)
|
|
28
|
-
) {
|
|
29
|
+
)) {
|
|
29
30
|
return true;
|
|
30
31
|
}
|
|
31
32
|
}
|