Incorrect Module Federation Configuration

Oct 13, 2025 by miodeya.com 116 views

Issue: Remote Component Fails to Render When Using Slots (Vue3 + Vite + Module Federation)

When loading a remote Vue component containing slots via Module Federation, the component fails to render. This issue is particularly frustrating as it prevents developers from utilizing the full potential of Vue's slot feature in their remote applications. In this article, we will delve into the problem, explore the possible causes, and provide a step-by-step guide to reproduce the issue.

To reproduce this issue, follow these steps:

Step 1: Configure a Remote App to Expose a Component with Slots

First, create a remote app that exposes a component with slots. For example, create a file called Counter.vue in the remote app directory with the following code:

<template>
  <!-- remote -->
  <button
    style="
      border: 0 solid #e2e8f0;
      margin-top: 10px;
      background-color: rgb(246, 179, 82);
      border-radius: 0.25rem;
      font-weight: 700;
      padding: 0.5rem 1rem 0.5rem 1rem;
      color: rgb(24, 24, 24);
    "
    @click="store.increment"
  >
    Remote counter: {{ count }}
    <p>
      <p>this is slot</p>
      <slot></slot>
    </p>
  </button>
</template>

Step 2: Use the Component in the Host Application

Next, use the component in the host application. Create a file called App.vue in the host application directory with the following code:

<script setup lang="ts">
import { defineAsyncComponent } from "vue";
import Counter from "./components/Counter.vue";
const RemoteMFE = defineAsyncComponent(
  // @ts-ignore
  () => import("remote/remote-app")
);
</script>

<template>
  <RemoteMFE v-if="!!RemoteMFE" />
</template>

You can find a reproduction repository for this issue on GitHub: https://github.com/neversleeppy/mf-vite-slot

This issue is specific to the following environment:

Framework: Vue3 + Vite
Module Federation: @module-federation/vite: "1.2.5"

When loading the remote component, you will encounter the following error message in the console:

TypeError: Cannot read properties of null (reading 'ce')

There are several possible causes for this issue:

Incorrect Module Federation Configuration: The Module Federation configuration might be incorrect, leading to the remote component not being loaded properly.
Missing or Incorrect Slot Definition: The slot definition in the remote component might be missing or incorrect, causing the component to fail to render.
Vue3 + Vite Compatibility Issues: There might be compatibility issues between Vue3 and Vite, leading to the remote component not being rendered correctly.

To troubleshoot this issue, follow these steps:

Check Module Federation Configuration: Verify that the Module Federation configuration is correct and that the remote component is being loaded properly.
Inspect Slot Definition: Inspect the slot definition in the remote component to ensure that it is correct and complete.
Verify Vue3 + Vite Compatibility: Verify that there are no compatibility issues between Vue3 and Vite.

In conclusion, the issue of a remote component failing to render when using slots in Vue3 + Vite + Module Federation is a complex problem that requires careful troubleshooting. By following the steps outlined in this article, developers can reproduce the issue and identify the possible causes. With the correct configuration and troubleshooting, developers can resolve this issue and ensure that their remote components render correctly.

Future work on this issue includes:

Improving Module Federation Configuration: Improving the Module Federation configuration to ensure that remote components are loaded correctly.
Enhancing Slot Definition: Enhancing the slot definition in remote components to ensure that they are rendered correctly.
Resolving Vue3 + Vite Compatibility Issues: Resolving any compatibility issues between Vue3 and Vite to ensure that remote components render correctly.

By addressing these areas, developers can ensure that their remote components render correctly and provide a seamless user experience.
Q&A: Issue with Remote Component Failing to Render When Using Slots (Vue3 + Vite + Module Federation)

In this article, we will address some of the frequently asked questions related to the issue of a remote component failing to render when using slots in Vue3 + Vite + Module Federation.

Q: What is the cause of the issue?

A: The cause of the issue is a complex problem that involves a combination of factors, including incorrect Module Federation configuration, missing or incorrect slot definition, and compatibility issues between Vue3 and Vite.

Q: How can I reproduce the issue?

A: To reproduce the issue, follow the steps outlined in the "Steps to Reproduce" section of the article. This includes configuring a remote app to expose a component with slots, using the component in the host application, and verifying that the issue is reproducible.

Q: What is the error message I see in the console?

A: The error message you see in the console is a TypeError: Cannot read properties of null (reading 'ce'). This error message indicates that there is an issue with the remote component not being loaded properly.

Q: How can I troubleshoot the issue?

A: To troubleshoot the issue, follow the steps outlined in the "Troubleshooting" section of the article. This includes checking the Module Federation configuration, inspecting the slot definition, and verifying Vue3 + Vite compatibility.

Q: What are some possible solutions to the issue?

A: Some possible solutions to the issue include:

Improving the Module Federation configuration to ensure that remote components are loaded correctly.
Enhancing the slot definition in remote components to ensure that they are rendered correctly.
Resolving any compatibility issues between Vue3 and Vite.

Q: Can I use a different version of Module Federation?

A: Yes, you can use a different version of Module Federation. However, it is recommended to use the latest version of Module Federation to ensure that you have the latest features and bug fixes.

Q: Can I use a different framework or library?

A: Yes, you can use a different framework or library. However, it is recommended to use Vue3 + Vite + Module Federation as it is a well-documented and widely used combination.

Q: How can I get help with the issue?

A: You can get help with the issue by:

Checking the official documentation for Vue3, Vite, and Module Federation.
Searching online forums and communities for similar issues.
Reaching out to the developers of Vue3, Vite, and Module Federation for support.

In conclusion, the issue of a remote component failing to render when using slots in Vue3 + Vite + Module Federation is a complex problem that requires careful troubleshooting. By following the steps outlined in this article and addressing the frequently asked questions, developers can reproduce the issue, identify the possible causes, and resolve the issue.

Future work on this issue includes:

Improving the Module Federation configuration to ensure that remote components are loaded correctly.
Enhancing the slot definition in remote components to ensure that they are rendered correctly.
Resolving any compatibility issues between Vue3 and Vite.

By addressing these areas, developers can ensure that their remote components render correctly and provide a seamless user experience.