Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

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

See original GitHub issue

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.

Issue Analytics

State:
Created 2 years ago
Comments:7 (3 by maintainers)

Top GitHub Comments

2reactions

lencxcommented, Apr 15, 2021

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

1reaction

lencxcommented, Apr 14, 2021

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)

Top Results From Across the Web

Vite 'base' option is ignored for the wasm output path #6 - GitHub

Our clients runs the app we're writing on some subfolders. So we have set the base config option in Vite to './' but...

Configuring Vite

If the config needs to conditional determine options based on the command ( dev / serve or ... Base public path when served...

Certain files not being bundled in ViteJS - Stack Overflow

This is not a bug but vite's Static Assets Handling behavior. Assets smaller in bytes than the assetsInlineLimit option will be inlined as...

Plugins - esbuild

This example demonstrates: working with binary data, creating virtual; modules using import statements, re-using the same path with different namespaces. This ...

Dockerfile reference - Docker Documentation

The FROM instruction initializes a new build stage and sets the Base Image ... Simply make a note of the last image ID...