vite optimize doesn't seem to actually be used with a subsequent vite

[segevfiner]

Describe the bug

Precompiling dependencies using vite optimize are not used by a subsequent vite dev server invocation.

Reproduction

https://stackblitz.com/edit/vitejs-vite-yydkbu?file=main.js

Steps to reproduce

1. Run vite optimize in a project that has external dependencies.
2. They will be generated into node_modules/.vite/deps_build-* instead of node_modules/.vite/deps, the manifest also has different hashes than the ones created from the Vite dev server.
3. The cache created by vite optimize is not used by a subsequent vite.

System Info

System:
    OS: macOS 12.6.1
    CPU: (10) arm64 Apple M1 Pro
    Memory: 120.06 MB / 16.00 GB
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 16.18.1 - ~/.nvm/versions/node/v16.18.1/bin/node
    npm: 9.1.1 - ~/.nvm/versions/node/v16.18.1/bin/npm
  Browsers:
    Chrome: 107.0.5304.110
    Safari: 16.1
  npmPackages:
    @vitejs/plugin-vue: ^3.1.2 => 3.2.0
    vite: ^3.1.7 => 3.2.3

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.

[github-actions]

Hello @segevfiner. We like your proposal/feedback and would appreciate a contribution via a Pull Request by you or another community member. We thank you in advance for your contribution and are looking forward to reviewing it!

[bluwy]

Looks like we need to make vite optimize prebundle for dev instead, or based on the optimizeDeps.disabled option.