[🐞] Qwik integration doesn't respect Astro config build.assetsPrefix

[ianrose]

Which component is affected?

Integration

Describe the bug

I am setting Astro's config with an assetsPrefix for build. This is being done to have the app's assets on a CDN.

...
  build: {
    inlineStylesheets: 'always',
    assetsPrefix: 'https://cdn.domain.com/myapp/',
  },
...

Non-qwik assets do have the correct prefixed path resolution however Qwik client scripts do not.

Reproduction

https://bolt.new/~/sb1-iixv7ivt

Steps to reproduce

Run npm run build npm run serve.

System Info

System:
    OS: macOS 15.3.1
    CPU: (10) arm64 Apple M1 Pro
    Memory: 139.64 MB / 16.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 22.14.0 - ~/.nvm/versions/node/v22.14.0/bin/node
    npm: 10.9.2 - ~/.nvm/versions/node/v22.14.0/bin/npm
    pnpm: 10.5.2 - /opt/homebrew/bin/pnpm
    bun: 1.2.4 - /opt/homebrew/bin/bun
  Browsers:
    Chrome: 137.0.7151.69
    Edge: 137.0.3296.68
    Safari: 18.3
  npmPackages:
    typescript: ^5.8.3 => 5.8.3

Additional Information

No response

[thejackshelton]

Hey @ianrose!

The bolt project provided seems to endlessly load for me.

I did just merge in a new API which allows you to change the base path that qwik uses for each Qwik Container that it creates.

https://github.com/QwikDev/astro/releases/tag/%40qwikdev%2Fastro%400.8.1

I'm with you on that Vite should be the source of truth. Ideally I would like to fix this in the vite plugin, move it out to the vite config with a migration script, but we'll see what happens.

For the time being, see if you can get the intended behavior through the renderOpts prop when adding a Qwik component from an Astro file.