Incorrect mkdist resolve relative imports with several entries

[alSergey]

Environment

• unbuild@3.6.0
• typescript@5.8.3
• node@v22.17.1

Reproduction

• Open StackBlitz
• Run npx unbuild
• Inspect the output files:
• • dist/common/fn.js (all correctly transformed)
• • dist/runtime/fn.js (import from src/common/ wasn't transformed)

Describe the bug

mkdist has built-in functionality for resolving relative imports, and it works great. You can see this in the dist/common/fn.js file.

import { COMMON_CONFIG } from "./config/index.js"; // correctly transformed
export const getConfig = () => {
  return COMMON_CONFIG;
};

Unfortunately, this functionality doesn't work when multiple entries are specified. This is evident in the dist/runtime/fn.js file. In that file, the import from src/runtime/ is correctly transformed, but the import from src/common/ remains unchanged.

import { COMMON_CONFIG } from "../common/config"; // wasn't transformed
import { RUNTIME_CONFIG } from "./config/index.js"; // correctly transformed
export const getCommonConfig = () => {
  return COMMON_CONFIG;
};
export const getRuntimeConfig = () => {
  return RUNTIME_CONFIG;
};

Is there a way to configure unbuild so that it properly resolves extensions when using multiple entries?

Additional context

No response

Logs

[alSergey]

Hi, are there any updates on this issue? I can’t find a way to work around this bug and have to write my own hacks, which is really inconvenient. It would be great to get a fix at the bundler level.

[kricsleo]

Each entry is compiled separately, and mkdist only parses relative path imports for files within the entry folder. Since the src/common/ folder is not in src/runtime/, it will not be resolved to the correct path for the src/runtime/ entry. I'm afraid you need to place it in the src/runtime/ folder.

[alSergey]

Hi, I understand why it works this way right now, but to me, this is a bundler bug. Here, multiple mkdist entries are specified, and in my view, they should all be processed within a single process. For example, this is how it works in rollup right now, which is why shared chunks are correctly generated for it.

Regarding your suggestion to move it to src/runtime/: that doesn’t work for me. My Nuxt module has roughly the following structure:

src
| - module.ts # Nuxt module
| - runtime/ # everything that runs at runtime
| - build/ # everything that runs at build time
| - common/ # shared code

If I move my code to src/runtime/, I will lose the semantics. I don’t want src/build/ to depend on src/runtime/