@module-federation/webpack-bundler-runtime
Module Federation Runtime for webpack
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Versions (showing 45 of 145)
| Version | Deps | Published |
|---|---|---|
| 0.2.7 | 2 / 1 | |
| 0.2.6 | 2 / 1 | |
| 0.2.5 | 2 / 1 | |
| 0.2.4 | 2 / 1 | |
| 0.2.3 | 2 / 1 | |
| 0.2.2 | 2 / 1 | |
| 0.2.1 | 2 / 1 | |
| 0.2.0 | 2 / 1 | |
| 0.1.21 | 2 / 1 | |
| 0.1.20 | 2 / 1 | |
| 0.1.19 | 2 / 1 | |
| 0.1.18 | 2 / 1 | |
| 0.1.17 | 2 / 1 | |
| 0.1.16 | 2 / 1 | |
| 0.1.15 | 2 / 1 | |
| 0.1.14 | 2 / 1 | |
| 0.1.13 | 2 / 0 | |
| 0.1.12 | 2 / 0 | |
| 0.1.11 | 2 / 0 | |
| 0.1.10 | 2 / 0 | |
| 0.1.9 | 2 / 0 | |
| 0.1.8 | 2 / 0 | |
| 0.1.7 | 2 / 0 | |
| 0.1.6 | 2 / 0 | |
| 0.1.5 | 2 / 0 | |
| 0.1.4 | 2 / 0 | |
| 0.1.3 | 2 / 0 | |
| 0.1.2 | 2 / 0 | |
| 0.1.1 | 2 / 0 | |
| 0.1.0 | 2 / 0 | |
| 0.0.17 | 2 / 0 | |
| 0.0.16 | 2 / 0 | |
| 0.0.15 | 2 / 0 | |
| 0.0.14 | 2 / 0 | |
| 0.0.13 | 2 / 0 | |
| 0.0.12 | 2 / 0 | |
| 0.0.11 | 2 / 0 | |
| 0.0.10 | 2 / 0 | |
| 0.0.9 | 2 / 0 | |
| 0.0.8 | 2 / 0 | |
| 0.0.7 | 1 / 0 | |
| 0.0.6 | 1 / 0 | |
| 0.0.5 | 1 / 0 | |
| 0.0.4 | 1 / 0 | |
| 0.0.3 | 1 / 0 |
v0.2.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.