You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Currently the build and prebundle steps use globs to find entry points, this is not optimal because globs can be slow on large folders and there is no way to pass virtual html files to vite
Describe the solution you'd like
Use the resolveId and load hooks to resolve html entry files, this would let users load virtual entry points without relying on a glob search
If no entry points are found using plugins, fallback to using a glob search
Frameworks built on top of vite wouldn't need to write a temporary html file and would use a virtual html file instead
Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Currently the build and prebundle steps use globs to find entry points, this is not optimal because globs can be slow on large folders and there is no way to pass virtual html files to vite
Describe the solution you'd like
Use the
resolveId
andload
hooks to resolve html entry files, this would let users load virtual entry points without relying on a glob searchIf no entry points are found using plugins, fallback to using a glob search
Frameworks built on top of vite wouldn't need to write a temporary html file and would use a virtual html file instead
Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered: