Bug: vp pack does not traverse upward to read pack configuration from vite.config.ts

[kangkangqvq]

Describe the bug

When using tsdown, if tsdown.config.ts is configured in the project root, running the tsdown command inside a subpackage will traverse upward and read the configuration from the root directory.

However, when using vp pack in vite-plus, the command does not traverse parent directories to read configuration defined in vite.config.ts.

It would be helpful if vp pack could support similar behavior: when executed inside a subdirectory (such as a subpackage in a monorepo), it should traverse upward and load configuration from the nearest vite.config.ts, including the pack configuration.

This would make it easier to use vite-plus in monorepo setups where the shared configuration is defined at the repository root.

Reproduction

null

Steps to reproduce

No response

System Info

vp pack

Used Package Manager

pnpm

Logs

Validations

• Read the Contributing Guidelines.
• Check that there isn't already an issue for the same bug.
• Confirm this is a Vite+ issue and not an upstream issue (Vite, Vitest, tsdown, Rolldown, or Oxc).
• The provided reproduction is a minimal reproducible example.

[fengmk2]

Can you provide a code repository to reproduce the issue?

[kangkangqvq]

Can you provide a code repository to reproduce the issue?能否提供一个可以重现该问题的代码仓库？

Add the pack configuration in vite.config.ts at the root directory.
Sub-packages do not have their own vite.config.ts.

When running vp pack directly inside a sub-package, the root configuration does not take effect.

This behavior occurs in any monorepo project.

[kazupon]

I might be able to reproduce this issue.
https://github.com/kazupon/vp-942-test

I've investigated the config resolution behavior.

Vite config resolution (loadConfigFromFile) only searches for config files (vite.config.ts, etc.) in the specified configRoot (which defaults to process.cwd()).
It does not traverse parent directories, if no config file is found in configRoot, it simply returns null.

vp pack calls resolveViteConfig(process.cwd()), which delegates to Vite's resolveConfig({ root: cwd }). So the current behavior, not reading a parent directory's vite.config.ts is consistent with Vite's own design.

So, As things stand, I seem the behavior described in this issue appears to be consistent with Vite's config resolution.