Failed to resolve workspace dependency present in 'optimizeDeps.include'

[tajo]

Describe the bug

It seems that optimizeDeps.include is able to resolve only dependencies that are defined in the root workspace and its package.json. In other words, you can optimize deps only from a single workspace.

After opening the repro, you will see this warning:

Failed to resolve dependency: jquery, present in 'optimizeDeps.include'

while react gets optimized just fine because it's in the root workspace.

Expectation

optimizeDeps.include should work for all dependencies across multiple workspaces. If these deps can be later resolved and served by Vite anyway I don't see a reason why they couldn't be prebundled as well.

Reproduction

https://stackblitz.com/edit/node-whfueq?file=app%2Fpackage.json

System Info

Stackblitz

Used Package Manager

pnpm

Logs

No response

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
• The provided reproduction is a minimal reproducible example of the bug.

[VRuzhentsov]

Here I found a solution from this guy

in several words - use Vite inside the workspace, not in the root

https://github.com/adiun/vite-monorepo

[tajo]

The example doesn't use optimizeDeps (it was removed)?

in several words - use Vite inside the workspace, not in the root
That's the case in my example as well.

[phiberber]

I've the same issue, With the following schema:

Package A:

• The one running Vite
• Has and uses B as dependency

Package B:

• Has as dependency a CJS package called C

When adding C to A's Vite optimizeDeps, Vite says it can't resolve the dependency. The more I see how Vite treats Workspaces, the less I want to use it.

[bluwy]

@phiberber Have you tried optimizeDeps.include: ['B > C'] as documented here?

@tajo The warning seems to be correct as you're starting the Vite server with the base set to pkg-a. Vite would then resolve dependencies from the root, which react exists in pkg-a, but not jquery.

[edisonLzy]

I've the same issue, With the following schema:

Package A:

• The one running Vite
• Has and uses B as dependency

Package B:

• Has as dependency a CJS package called C

When adding C to A's Vite optimizeDeps, Vite says it can't resolve the dependency. The more I see how Vite treats Workspaces, the less I want to use it.

i got this issue too!

[bluwy]

Going to close this following my comment above.