When specifying the PackageDirectory property in ViteOptions, treat non-rooted directory paths as though they are relative to the IWebHostEnvironment.ContentRootPath. This path will be the Project directory when running during development.
Fixes #44
I tested this with a project structure like below, where the Vite client application (both package.json and vite.config.js) are within a child folder of the package directory:
I also tested with a folder structure that has the Vite client application outside the project directory entirely (similar to Webcoda's project in the bug report).
When specifying the
PackageDirectory
property in ViteOptions, treat non-rooted directory paths as though they are relative to theIWebHostEnvironment.ContentRootPath
. This path will be the Project directory when running during development.Fixes #44
I tested this with a project structure like below, where the Vite client application (both package.json and vite.config.js) are within a child folder of the package directory:
I also tested with a folder structure that has the Vite client application outside the project directory entirely (similar to Webcoda's project in the bug report).