logologo
Guide
Practice
Configuration
Plugins
Showcase
Blog
Ecosystem
Module Federation Examples
Practical Module Federation
Zephyr Cloud
Nx
简体中文
English
Guide
Practice
Configuration
Plugins
Showcase
Blog
Module Federation Examples
Practical Module Federation
Zephyr Cloud
Nx
简体中文
English
logologo

Getting Started

Introduction
Setting Up the Environment
Quick Start Guide
Feature Navigation
Glossary of Terms
npm Packages

basic

Runtime

Runtime Access
Runtime API
Runtime Hooks
Rsbuild Plugin
Rspack Plugin
Webpack Plugin
Rspress Plugin
Vite Plugin
Metro
Type Hinting
Command Line Tool
Style Isolation

Data Solution

Data Fetching
Data Caching
Prefetch

Frameworks

Modern.js
Next.js

Deployment

Deploy with Zephyr Cloud

Debug

Enable debug mode
Chrome DevTools
Global variables

Troubleshooting

Overview

Runtime

RUNTIME-001
RUNTIME-002
RUNTIME-003
RUNTIME-004
RUNTIME-005
RUNTIME-006
RUNTIME-007
RUNTIME-008
RUNTIME-009

Build

BUILD-001
BUILD-002

Type

Overview
TYPE-001
Other
Edit this page on GitHub
Previous PageOverview
Next PageRUNTIME-002

Failed to get remoteEntry exports.

  • Error Code: RUNTIME-001

#Reasons

When the producer entry file is loaded normally, the producer will be registered in the global object (globalThis/window), which can be accessed through window[remoteEntryKey].

However, during this loading process, registered producers are inaccessible. There are three possible causes for this error:

  1. The remoteEntryUrl is not right.
  2. The remoteEntry file does not mount the container correctly.
  3. Network problem, the resource cannot be accessed.
  4. The remote type is a different format and not specified in either the plugin or in the init for the remotes details.

#Solutions

There are corresponding solutions for the reasons:

  1. Check whether the remoteEntryUrl is correct.
  • If using manifest, check the publicPath and remoteEntry.name fields in the manifest
  1. If the project builder is rspack, check whether runtimeChunk is set in the final build configuration. If so, delete this configuration.
  2. Check if the resource is externally accessible.
  3. Loading a ESM remote from a non-esm host
  • setting type: 'module' on the remote config