I used the $settings['vite'] method in settings.php to set global values for vite because I have distributed libraries but they all get bundled at the root of the project.
The problem I'm facing is that I can't tell vite that the manifest is at ./.vite/manifest.json because the location of the library being processed is always prepended to that.
I'd like the settings version to use a project-relative value, which will probably break existing usages. I've worked out a way around it which is to list the manifest as something like manifest: '../../../../.vite/manifest.json' in every library definition, but it's not the best DX so I thought I'd bring it up to see what the community thinks?
Active
1.0
Code
I can no longer do without this because SDCs cannot designate their own manifest path as far as I can tell.
I've had to find another way to support SDCs in my project. I've created an MR to show this functionality though as I still think it is better that an override is absolute rather than relative.