@softarc/native-federation 2.0.8

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@2.0.8 was published on 2024-02-05. Its manifest declares 3 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 2.0.8 · View npm registry JSON · Latest release

Package specifications

Version2.0.8
License declarationNot declared
Published2024-02-05T09:24:14.126Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count3
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size114.89 KiB
Published file count84
Package typecommonjs
ES module entryNot declared
Default entry./src/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies24
Repository starsUnknown
Repository forksUnknown

Install @softarc/native-federation 2.0.8

npm install @softarc/native-federation@2.0.8
pnpm add @softarc/native-federation@2.0.8
yarn add @softarc/native-federation@2.0.8

Runtime dependencies

Peer requirements

  • None declared

Optional dependencies

  • None declared

Resolved dependency graph

This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.

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