[Module Federation] Failing to determine SWR version

[Erazihel]

Bug report

Description / Observed Behavior

Failing to determine what SWR version to use with Module Federation based on Webpack & SWR 2.0.

Expected Behavior

No warning nor error should be displayed / thrown when using SWR with Module Federation.

Additional Context

Everything was working great with SWR 1.3.0.

Here is the prompted warning:

WARNING in shared module swr -> .../node_modules/swr/core/dist/index.mjs

No version specified and unable to automatically determine one. No version in description file (usually package.json).
Add version to description file .../node_modules/swr/core/package.json, or manually specify version in shared config.

(Note that the version is already specified in the shared config)

And this is the error thrown:

Uncaught (in promise) Error: Unsatisfied version 0 from micro-frontends of shared singleton module swr (required =2.0.0)

After manually adding a version to the node_modules/swr/core/package.json file, it seems that everything is working as expected but this is not a viable fix.

[hongkiulam]

+1

[wjkawecki]

+1

[Matikun]

+1
i tried this : After manually adding a version to the node_modules/swr/core/package.json file, it seems that everything is working as expected but this is not a viable fix.
However, I'm still getting the warnings.

[martinbobbio]

+1

[nicolaswww]

Any news on this request? thank you!

[WizzApp]

We are having this problem as well, this makes SWR essentially unusable with a Webpack Module Federation setup for us.
I have a bit of time on my hands right now and could probably create a PR to fix this, if this is ok.

[francosalcedo]

+1

[kobayuri]

+1

[kobayuri]

As a fast fix/unblock:

      swr: {
        singleton: true,
        strictVersion: true,
        requiredVersion: '0', // Dumb fix
      };

[chaos1ee]

+1

[yamaoto]

Also you can temporary fix it with https://www.npmjs.com/package/patch-package

For error:

WARNING in shared module swr -> .../node_modules/swr/core/dist/index.mjs

No version specified and unable to automatically determine one. No version in description file (usually package.json).
Add version to description file .../node_modules/swr/core/package.json, or manually specify version in shared config.

1. Open .../node_modules/swr/core/package.json for edit
2. Manually write version from your dependency

{
  "main": "./dist/index.js",
  "module": "./dist/index.esm.js",
  "types": "./dist/index.d.ts",
+ "version": "2.2.4",

3. Generate patch file:

npx patch-package swr

5. Install patch-package in devDependencies
6. Add new script in your package.json

 "scripts": {
+  "postinstall": "patch-package"
 }

This script will run for every package installation and you can share this patch for your team

[koba04]

We updated our bundle convention at #2865.
Unfortunately, this hasn't been released yet, but the change might solve this problem.
I haven't tested this, I might be wrong.

[koba04]

Could you try v2.2.5? This includes #2356 (comment)

[yamaoto]

@koba04
Tried to test on my project with Module Federation on the new v2.2.5 everything works great and without any hacks in .
Thank you very much for the notification.

[koba04]

I'll close this as fixed. Please reopen this if you still have a problem with v2.2.5