@softarc/native-federation 3.5.4
Native Federation is a "browser-native" implementation of the successful mental model behind wepback Module Federation for building Micro Frontends and plugin-based solutions. It can be **used with any framework and build tool** for implementing **Micro F
@softarc/native-federation@3.5.4 was published on 2026-03-06. Its manifest declares 5 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.
All @softarc/native-federation versions · Permanent reference to 3.5.4 · View npm registry JSON · Latest release
Package specifications
| Version | 3.5.4 |
|---|---|
| License declaration | MIT |
| Published | 2026-03-06T09:19:31.392Z |
| Node.js requirement | Not declared |
| Type declarations | Bundled declarations |
| Runtime dependency count | 5 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | 195.89 KiB |
| Published file count | 114 |
| Package type | commonjs |
| ES module entry | Not declared |
| Default entry | ./src/index.js |
| Side effects declaration | Not declared |
| Direct advisories | Unknown |
| Resolved graph dependencies | Unknown |
| Repository stars | Unknown |
| Repository forks | Unknown |
Install @softarc/native-federation 3.5.4
npm install @softarc/native-federation@3.5.4 pnpm add @softarc/native-federation@3.5.4 yarn add @softarc/native-federation@3.5.4
Runtime dependencies
- chalk ^5.6.2
- json5 ^2.2.0
- fast-glob ^3.3.3
- @softarc/sheriff-core ^0.19.2
- @softarc/native-federation-runtime ~3.5.4
Peer requirements
- None declared
Optional dependencies
- None declared
How to interpret the specifications
Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.
Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.
Evidence and freshness
- Readable npm registry JSON — retrieved 2026-11-01T20:55:44.663Z