Vite 3 - force-including unknown dependency bombs out

[bholmesdev]

Describe the bug

In Vite 2, force-including an unknown dependency via optimizedDeps.include or ssr.noExternal would log a warning only. In Vite 3, the dev server / production build bombs out with the error:

error during build:
Error: Failed to resolve force included dependency: banana
    at addManuallyIncludedOptimizeDeps (file:///home/projects/vitejs-vite-ecaudg/node_modules/vite/dist/node/chunks/dep-332aa27f.js:38515:27)
    at async initialProjectDependencies (file:///home/projects/vitejs-vite-ecaudg/node_modules/vite/dist/node/chunks/dep-332aa27f.js:38313:5)
    at async initDepsOptimizer (file:///home/projects/vitejs-vite-ecaudg/node_modules/vite/dist/node/chunks/dep-332aa27f.js:37812:32)
    at async doBuild (file:///home/projects/vitejs-vite-ecaudg/node_modules/vite/dist/node/chunks/dep-332aa27f.js:43100:9)
    at async build (file:///home/projects/vitejs-vite-ecaudg/node_modules/vite/dist/node/chunks/dep-332aa27f.js:43062:16)
    at async CAC.eval (file:///home/projects/vitejs-vite-ecaudg/node_modules/vite/dist/node/cli.js:758:9)

Reproduction

https://stackblitz.com/edit/vitejs-vite-ecaudg?file=vite.config.js&terminal=dev

System Info

System:
    OS: macOS 12.0.1
    CPU: (8) arm64 Apple M1
    Memory: 108.19 MB / 16.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 18.4.0 - ~/.nvm/versions/node/v18.4.0/bin/node
    Yarn: 1.22.18 - /usr/local/bin/yarn
    npm: 8.12.1 - ~/.nvm/versions/node/v18.4.0/bin/npm
  Browsers:
    Chrome: 103.0.5060.53
    Firefox: 95.0
    Safari: 15.1

Used Package Manager

npm

Logs

Click to expand!

❯ npm run build
$ vite build
vite v3.0.0-beta.5 building for production...
error during build:
Error: Failed to resolve force included dependency: banana
    at addManuallyIncludedOptimizeDeps (file:///home/projects/vitejs-vite-ecaudg/node_modules/vite/dist/node/chunks/dep-332aa27f.js:38515:27)
    at async initialProjectDependencies (file:///home/projects/vitejs-vite-ecaudg/node_modules/vite/dist/node/chunks/dep-332aa27f.js:38313:5)
    at async initDepsOptimizer (file:///home/projects/vitejs-vite-ecaudg/node_modules/vite/dist/node/chunks/dep-332aa27f.js:37812:32)
    at async doBuild (file:///home/projects/vitejs-vite-ecaudg/node_modules/vite/dist/node/chunks/dep-332aa27f.js:43100:9)
    at async build (file:///home/projects/vitejs-vite-ecaudg/node_modules/vite/dist/node/chunks/dep-332aa27f.js:43062:16)
    at async CAC.eval (file:///home/projects/vitejs-vite-ecaudg/node_modules/vite/dist/node/cli.js:758:9)

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.

[btea]

It seems have been fixed by #8917

[bluwy]

Can confirm running npm i vite@beta && npm run dev in the repro it's fixed.