Modules with .server.js becomes different empty files on client build

[sergiodxa]

When importing a module with the .server prefix they are replaced with something like this:

import {
  __commonJS,
  init_react
} from "/build/_shared/chunk-DOM5QJLA.js";

// empty-module:../services/auth0.server
var require_auth0 = __commonJS((exports, module) => {
  init_react();
  module.exports = {};
});

export {
  require_auth0
};

If I import more than one server-only module and go to the browser I see the same amount of different JS files with an almost identical content (specially on prod builds) which are all being loaded in parallel.

Ideal:

If the import can't be removed at least they are replaced with a single placeholder empty module that's only loaded once and shared by all modules importing a server-only module.

[chaance]

@sergiodxa Combing through old issues, is this one still relevant?

[rphlmr]

Hi,
Coming here by chance, looking for info about these empty modules.
I can confirm that every empty module is a downloaded chunk (in production, too).

Is it expected ?

[alexblack]

This is an issue for us, we have many empty chunks being loaded by the browser in production, and increasing the download size of the manifest file that is also downloaded by the browser.

It seems like this should be fixed, empty chunks shouldn't be a thing, should it?