Static resources mapping issue in packaging process
DDDPG opened this issue · 1 comments
DDDPG commented
When packaging, in vite.config.ts, import the env VITE_PUBLIC_PATH as public basic dir, but the static resource in dist folder did not changed correspondingly, because assetsDir was “static”, which is static, I think it is supposed to be VITE_PUBLIC_PATH.slice(1, -1) then the path mapping is right. From my point of view this is more convinent than memorizing the static mapping rules in DockerFIle or other files.
Apology for the interruption few days ago of merging request issue.🏳️
pany-ang commented
"assetsDir" doesn't seem to need to be synchronized with "VITE_PUBLIC_PATH". I don't particularly understand the scenario you mentioned