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
Without setting ViteOptions.Manifest, it should be .vite/manifest.json according to the documentation. If I do the following in a controller, True is written to the console as expected:
…so it's clear that the file .vite/manifest.json exists. However, when I inspect the IViteManifest, it returns no results:
How should I go about debugging this? It feels like the ViteManifest should not construct its own instance of PhysicalFileProvider, but instead use the one exposed on environment.
Hello, did you set a subfolder as output folder? Example: wwwroot/dist? If that's the case, then you need to configure the base option or the package won't be able to find your manifest file. See more in the Wiki.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Without setting
ViteOptions.Manifest, it should be.vite/manifest.jsonaccording to the documentation. If I do the following in a controller,Trueis written to the console as expected:…so it's clear that the file
.vite/manifest.jsonexists. However, when I inspect theIViteManifest, it returns no results:How should I go about debugging this? It feels like the
ViteManifestshould not construct its own instance ofPhysicalFileProvider, but instead use the one exposed onenvironment.Vite.AspNetCore/src/Vite.AspNetCore/Services/ViteManifest.cs
Line 65 in 0c05a6b
But I'm not sure if this would fix the problem or what the problem actually is. Thoughts?
All reactions