[🐞] qwik-city: vite base doesn't work in dev mode

[wmertens]

Which component is affected?

Qwik City (routing)

Describe the bug

When you set config.base of vite, the build correctly uses it but dev mode breaks, getting module files without the base path.

Reproduction

https://stackblitz.com/edit/qwik-starter-wvwual?file=vite.config.ts

Steps to reproduce

try clicking Home

System Info

stackblitz, 1.5.1

Additional Information

No response

[wmertens]

Workaround: In your vite config, use

export default defineConfig(({command, mode}) => {
    return {
        base: command === 'build' ? '/your-base/' : undefined,
// ...

[JerryWu1234]

let me pick this up.,

[JerryWu1234]

you say this bug ?

[wmertens]

@JerryWu1234 yes it should use the import.meta.env.BASE_URL in front of it

[JuanmaVargas]

In production, is there any workaround to fix this? I'm trying to create a multi-zone in Next.js for a Qwik application, and for that, I need the vite.base set in the configuration to work for all the assets

[wmertens]

@JuanmaVargas do you mean it's not working in production?

I have the fix for dev in #6326 but it's part of a rewrite. I hope to land it soon.

[JohnPremKumar]

Meantime if anyone looking for workaround set different path production and development:

export default defineConfig(() => {
  return {
    base: process.env.NODE_ENV === 'production' ? `/production-path/` : '',
    plugins: [
      qwikCity(),
      qwikVite(),
      tsconfigPaths(),
      vanillaExtractPlugin(),
    ],
  };
});

[wmertens]

I believe this to be fixed in 1.7.1. There are still some problems with windows though, see #6676