-
Describe the bugWhile trying to migrate my webpack app to Vite, I'm getting this output:
Vite then goes on to list every HTML file in my repo for some reason. It shouldn't even be considering these files, because (a) they're documentation and (b) they're in my ReproductionN/A Steps to reproduceNo response System InfoSystem:
OS: Windows 10 10.0.22621
CPU: (8) x64 11th Gen Intel(R) Core(TM) i7-1185G7 @ 3.00GHz
Memory: 5.35 GB / 15.71 GB
Binaries:
Node: 16.19.1 - C:\Program Files\Node.js\node.EXE
npm: 9.6.2 - C:\Program Files\Node.js\npm.CMD
Browsers:
Edge: Spartan (44.22621.1702.0), Chromium (113.0.1774.50)
Internet Explorer: 11.0.22621.1
npmPackages:
@vitejs/plugin-react: 4.0.0 => 4.0.0
vite: 4.3.8 => 4.3.8 Used Package Managerpnpm LogsNo response Validations
|
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 5 replies
-
Vite treats all possible HTML files as entries by default during scanning (a simple If that's not desirable, you can configure |
Beta Was this translation helpful? Give feedback.
-
bonjour à tous svp comment je peux resoudre ça ? |
Beta Was this translation helpful? Give feedback.
-
All i had to do was just to:
|
Beta Was this translation helpful? Give feedback.
-
I had a similar issue ( |
Beta Was this translation helpful? Give feedback.
Vite treats all possible HTML files as entries by default during scanning (a simple
**/*.html
glob from Vite root), since technically you can access/packages/cv-resource/docs/index.html
from the Vite project too.If that's not desirable, you can configure
optimizeDeps.entries
to change the entries. Maybe we can update the error message to showoptimizeDeps.entries
if you'd like to contribute.