Vite 'base' option is ignored for the wasm output path

[maccesch]

Our clients runs the app we're writing on some subfolders. So we have set the base config option in Vite to './' but the wasm file is still loaded from the root '/our_wasm_bg.xxxxx.wasm'. We tried to set base = '/test/' but the wasm file is referenced absolutely without that.

[lencx]

This problem is fixed in the v1.2.8 (#4)version, please try again after upgrading.

vite doc: https://vitejs.dev/config/#base

Base public path when served in development or production. Valid values include:

• Absolute URL pathname, e.g. /foo/
• Full URL, e.g. https://foo.com/
• Empty string or ./ (for embedded deployment)

[maccesch]

That was fast! Thanks, man!

[sauloco]

The new 1.3.0 gives me the next output:
[rsw::error] wasm-pack for crate wasm failed

But if I downgrade to 1.2.7 works ok.

I've been diving through the code and looks like root and crate paths aren't pointing to the actual path bc of an issue. Please consider checking my suggestion in #7

[lencx]

@sauloco Please install version v1.3.1, try again.

[sauloco]

Already tested, working ok and delivered. 👌🏻
Thanks so much for your help!

[maccesch]

in 1.3.1 it seems that absolute base paths work but not relative. When I have base: '/dist/' it works but when I have base: './' then although the build log indicates everything is correct in the browser it still tries to load from /assets/xxxx_bg.wasm

[lencx]

@maccesch, I tried this seems to be ok.
yarn build --base "./"

build

<!-- dist/index.html -->
<script type="module" crossorigin src="./assets/index.21e4292b.js"></script>
<link rel="modulepreload" href="./assets/vendor.77fab89d.js">
<link rel="stylesheet" href="./assets/index.41fe33df.css">

// dist/assets/chasm.f9b73bca.js
new URL("./assets/rsw~chasm_bg.7b76064a.wasm",location.origin)