Creating a minimal-size remote project without preload-helper dependency

[mairas]

Hi,

I'm using Preact+bootstrap to create a configuration UI for an ESP32 embedded device. The device will operate on boats, so internet connectivity can't be guaranteed, and all served files need to be stored on the embedded device itself.

I'm trying to use vite-plugin-federation to implement a plugin system for the project: the host side is part of a toolkit library (SensESP), while the remotes are used to add new pages and config components to the UI. At the moment, I am playing with the remote side project. I have a remote that is built successfully with a dist/assets/test-plugin.js bundle file. However, test-plugin.js always has the following import:

import { _ as __vitePreload } from "./preload-helper-2d04bc7d.js";

I have tried removing all css files and assets from the remote project but the file still gets added. Given that it's 1.8 KB of code that, I believe, only exists for CSS preloading, I'd rather have it removed. Can I somehow do that? (And is this a vite issue to begin with?)

This is the plugin component I am trying to share (for now):

function TestPlugin() {
  return <div>This is a <strong>test plugin</strong> component!</div>;
}

export default TestPlugin;

My vite.config.js file is below:

import { defineConfig } from 'vite'
import preact from '@preact/preset-vite'
import federation from "@originjs/vite-plugin-federation";

// https://vitejs.dev/config/
export default defineConfig({
  plugins: [
    preact(),
    federation({
      name: 'plugin',
      filename: 'test-plugin.js',
      // Modules to expose
      exposes: {
        './TestPlugin': './src/test-plugin.jsx',
      },
      shared: ['preact', 'bootstrap', 'immer',]
    })],
    build: {
      modulePreload: false,
      minify: false,
      cssCodeSplit: false,
      target: 'es2022',
      rollupOptions: {
        // specify the output options
        external: ['preact', 'bootstrap', 'immer'], // Peer dependencies
      }
    }
})

[mairas]

Replying to myself: this is essentially a vite issue, tracked here: vitejs/vite#13952