The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →In Native Federation, the path from federation.config.js to remoteEntry.json runs through a Core federation builder and a bundler adapter: describe the remote and its dependencies, run the application bundler with federation externals preserved, then build the federation artifacts. At runtime, the host reads the JSON entry to resolve and load exposed modules. The current Core README identifies v4, while the detailed lifecycle and artifact descriptions cited here are in the Core v3 documentation; verify version-sensitive options against your installed packages.
What the configuration describes
A remote’s federation.config.js identifies the remote and the modules it makes available. The central fields are a name, an exposes map from public keys such as ./component to source files, and shared dependency settings. The Native Federation configuration reference also documents internal shared mappings, packages to skip, extra externals, and feature options.
As an Amazon Associate I earn from qualifying purchases.
Sharing syntax and defaults can depend on the Core and framework adapter versions. The v3 reference uses share or shareAll for sharing; check the configuration reference for the versions in your project before copying an example or assuming a default.
How the build is ordered
The Core is designed to work with different frameworks and bundlers. A bundler-specific adapter connects it to the application build. In the current Core repository README, the esbuild example initializes a federation builder with workspace options including workspaceRoot, outputPath, tsConfig, and federationConfig. It then uses the builder’s externals when running the application bundler and calls the federation build afterward.
#1 Best Overall
- GIGABIT ETHERNET PORTS: Features 5 x 1.0Gbps Ethernet ports for high-speed connectivity. Auto-negotiating ports detect the optimal speed for connected devices and work with existing Cat5e or Cat6 Ethernet cables.
- PLUG-AND-PLAY UNMANAGED NETWORK SWITCH: Simple plug-and-play setup with no software to install or configuration required.
- FLEXIBLE MOUNTING OPTIONS: Compact metal design supports desktop or wall-mount placement for versatile installation.
- SILENT & ENERGY-EFFICIENT OPERATION: Fanless design ensures silent performance, while IEEE 802.3az Energy Efficient Ethernet reduces power consumption without compromising high-speed network performance.
- REGIONAL COMPATIBILITY: Made for use in U.S. & CA only
- Initialize the builder. Pass the workspace and configuration options required by the adapter, including the path to
federation.config.js. - Run the application bundler. Keep
federationBuilder.externalsexternal, rather than allowing the application bundle to inline packages that federation should resolve through its import map. - Build federation artifacts. Call
federationBuilder.build()after the application bundler finishes.
This order is part of the integration contract: initializing alone does not produce the federation metadata, and running the federation build before the application bundler would not follow the documented sequence.
What the federation build emits
The Core v3 build-process documentation describes three phases:
Rank #2
- 𝗢𝗻𝗲 𝗦𝘄𝗶𝘁𝗰𝗵 𝗠𝗮𝗱𝗲 𝘁𝗼 𝗘𝘅𝗽𝗮𝗻𝗱 𝗡𝗲𝘁𝘄𝗼𝗿𝗸: 5× 10/100/1000Mbps RJ45 Ports supporting Auto Negotiation and Auto MDI/MDIX.
- 𝗚𝗶𝗴𝗮𝗯𝗶𝘁 𝘁𝗵𝗮𝘁 𝗦𝗮𝘃𝗲𝘀 𝗘𝗻𝗲𝗿𝗴𝘆: Latest innovative energy-efficient technology greatly expands your network capacity with much less power consumption and helps save money.
- 𝗥𝗲𝗹𝗶𝗮𝗯𝗹𝗲 𝗮𝗻𝗱 𝗤𝘂𝗶𝗲𝘁: IEEE 802.3X flow control provides reliable data transfer and Fanless design ensures quiet operation.
- 𝗣𝗹𝘂𝗴 𝗮𝗻𝗱 𝗣𝗹𝗮𝘆: Easy setup with no software installation or configuration needed.
- 𝗔𝗱𝘃𝗮𝗻𝗰𝗲𝗱 𝗦𝗼𝗳𝘁𝘄𝗮𝗿𝗲 𝗙𝗲𝗮𝘁𝘂𝗿𝗲𝘀: Prioritize your traffic and guarantee high quality of video or voice data transmission with Port-based 802.1p/DSCP QoS and IGMP Snooping.
- Bundle exposed modules and shared mappings.
- Bundle shared packages, with browser or Node and default or separate groupings described by that version’s implementation.
- Write federation metadata to
remoteEntry.jsonand a companionimportmap.json.
The same v3 page says production output filenames may be hashed, while development filenames are stable. These are implementation details documented for Core v3, not guarantees for every adapter or later release.
Shared-package caching in the documented v3 process
The v3 build-process page describes a cache at node_modules/.cache/native-federation/<project>/. Its metadata includes a checksum over shared keys and versions plus the development flag. When a group is unchanged, it may be reused; changes invalidate and rebuild the affected group. The page also describes watch-mode integrations skipping shared-package bundling on later rebuilds when shared packages have not changed. Treat this as a documented optimization, not behavior guaranteed across all versions and adapters.
Rank #3
- GIGABIT ETHERNET PORTS: Features 8 x 1.0Gbps Ethernet ports for high-speed connectivity. Auto-negotiating ports detect the optimal speed for connected devices and work with existing Cat5e or Cat6 Ethernet cables.
- PLUG-AND-PLAY UNMANAGED NETWORK SWITCH: Simple plug-and-play setup with no software to install or configuration required.
- FLEXIBLE MOUNTING OPTIONS: Compact metal design supports desktop or wall-mount placement for versatile installation.
- SILENT & ENERGY-EFFICIENT OPERATION: Fanless design ensures silent performance, while IEEE 802.3az Energy Efficient Ethernet reduces power consumption without compromising high-speed network performance.
- REGIONAL COMPATIBILITY: Made for use in U.S. & CA only
What is inside remoteEntry.json
The Core v3 artifact reference documents a JSON object with name, exposes, and shared. Development builds can also include buildNotificationsEndpoint when notifications are enabled.
name: the remote’s identity.exposes: public module keys and the emitted file for each exposed module.shared: shared package details, which can include package name, emitted file, required and concrete versions, singleton behavior, and strict-version behavior.
Asset filenames in the entry are relative to the entry’s directory. The host or runtime can therefore fetch remoteEntry.json and resolve an emitted filename against the directory containing that entry, rather than needing a separately hard-coded asset base for every file.
Rank #4
- 【One Switch Made to Expand Network】Features 5 RJ45 ports with 10/100/1000Mbps speeds, supporting Auto-Negotiation and Auto MDI/MDIX for hassle-free setup. Ideal for expanding your network, with 1 uplink (input) port and 4 output ports to split your Ethernet connection to multiple devices.
- 【Gigabit that Saves Energy】Latest innovative energy-efficient technology greatly expands your network capacity with much less power consumption and helps save money
- 【Reliable and Quiet】IEEE 802.3X flow control provides reliable data transfer and Fanless design ensures quiet operation
- 【Plug and Play】Easy setup with no software installation or configuration needed
- 【Ethernet Splitter】Connect to your router or modem for additional wired connections (laptop, gaming console, printer, etc)
Why importmap.json is also present
importmap.json is a flat package-name-to-output-file mapping derived from the shared list. The v3 artifact reference says the Native Federation runtime builds its import map from remoteEntry.json; the separate file is available to tooling or host integrations that need the simpler mapping.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesHow a host uses the entry at runtime
A host is the application that loads remotes. A deployment manifest can map remote names to their remoteEntry.json URLs, keeping environment-specific locations outside the application’s source code. The terminology reference describes this host-and-manifest model.
Best Value
- 𝗘𝗶𝗴𝗵𝘁 𝟮.𝟱 𝗚𝗯𝗽𝘀 𝗣𝗼𝗿𝘁𝘀 𝗳𝗼𝗿 𝗦𝘂𝗽𝗲𝗿-𝗙𝗮𝘀𝘁 𝗖𝗼𝗻𝗻𝗲𝗰𝘁𝗶𝗼𝗻𝘀: 8× 2.5-Gigabit ports unlock the highest performance of your Multi-Gig bandwidth and devices, and provide up to 40 Gbps of switching capacity.
- 𝗔𝘂𝘁𝗼-𝗡𝗲𝗴𝗼𝘁𝗶𝗮𝘁𝗶𝗼𝗻: Auto-negotiation intelligently senses the link speeds and adjusts between 3-speeds (100Mb/1G/2.5G) for compatibility and optimal performance for all your devices, including 2.5G WiFi 6 AP, 2.5G NAS, 2.5G PCIe Adapter, 2.5G Server, gaming computer, 4K video, and more.
- 𝗜𝗱𝗲𝗮𝗹 𝗳𝗼𝗿 𝗩𝗮𝗿𝗶𝗼𝘂𝘀 𝗦𝗰𝗲𝗻𝗮𝗿𝗶𝗼𝘀: Built for LAN parties, home entertainment, small and home offices, and instant transfer for workstations.
- 𝗛𝗮𝘀𝘀𝗹𝗲-𝗙𝗿𝗲𝗲 𝗖𝗮𝗯𝗹𝗶𝗻𝗴: Instantly upgrade to 2.5 Gbps without the need to upgrade to Cat6 wiring, reducing wiring costs and hassle. *
- 𝗦𝗶𝗹𝗲𝗻𝘁 𝗢𝗽𝗲𝗿𝗮𝘁𝗶𝗼𝗻: Industry-leading fanless design ensures silent operation, ideal for any home or business.
The Core v3 getting-started guide demonstrates passing a manifest of remote names and entry URLs to initFederation, then loading an exposed module with loadRemoteModule. For example, a manifest entry associates a remote name with the URL of its JSON entry; after initialization, the host can request an exposed key such as ./component.
The guide also calls out es-module-shims and recommends a bootstrap split: code that touches shared dependencies should not execute until the promise returned by initFederation resolves. Otherwise, application code may run before federation has established the resolutions it needs.
Native Federation JSON entry is not Webpack’s JS container
Do not treat Native Federation’s remoteEntry.json as a renamed version of Webpack Module Federation’s entry. The Webpack ModuleFederationPlugin documentation describes a different integration whose conventional container entry is remoteEntry.js. Native Federation’s documented flow uses JSON metadata, a bundler adapter, and runtime import-map resolution. The filename similarity is not evidence that the build steps or runtime contracts are interchangeable.
Recommended Free Tools
Version checks before adapting an example
The current Core repository README identifies the project as v4 and demonstrates the configuration-to-builder-to-entry sequence. The detailed build-process, artifact, configuration, and getting-started pages linked above are under the v3 documentation path. Before applying their exact option names, defaults, output details, or caching behavior, compare them with the Core and adapter versions installed in your project.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
