Stabilizing optimizeDeps.noDiscovery

[patak-dev]

optimizeDeps.noDiscovery

• Introduced in [email protected]
• Rationale in Original PR
• No docs

  /*
   * Automatic dependency discovery. When `noDiscovery` is true, only dependencies 
   * listed in `include` will be optimized. The scanner isn't run for cold start 
   * in this case. CJS-only dependencies must be present in `include` during dev.
   * @default false
   * @experimental
   */
  noDiscovery?: boolean

• Used by Vitest

Starting a discussion to gather feedback so we can stabilize this feature. If Vitest 1.0 is going to depend on it, I think we should move it out of experimental in Vite 5. cc @sheremet-va in case you have some new feedback about how this feature is working in Vitest.

[sheremet-va]

Vitest relies on it for deps.optimizer, but we don't enforce it yet. 0.34.0 should deprecate old deps.inline in favor of optimizer. This should give us more feedback on the actual usage.