Yet another question about building without index.html

[gohryt]

I have a project which is spa, it have a very basic structure:

/project-go/
  many_go_files_inside
  ...
/project-js/
  package.json
  public/some_assets
  src/index.tsx
  src/some_ts_files
  src/...
  src/assets/some_png_images
  index.html
  vite.config.ts

When i developing frontend part of this project i need this index.html because of possibility to run it and watch changes in browser in real time.
When i building it for serving from backend i don't need in index.html, it will be generated by my golang backend, but i need all other files from frontend.

I wrote this

import { defineConfig } from 'vite'
import react from '@vitejs/plugin-react'

export default defineConfig({
  plugins: [react()],
  build: {
    rollupOptions: {
      input: '/src/index.tsx',
      output: {
        format: 'iife',
        dir: 'build',
        entryFileNames: 'build.js'
      }
    }
  }
});

config in vite.config.ts file as was recommended in this discussion and it works very close to behavior i need.

The problem is that given config builds with structure

/build/build.js
/build/assets/some_png_images

when generated js asks for this assets from

/assets/some_png_images

path.
I can't believe that there is no solution for normal spa building and bundling with vite.
Will be happy with some help.

[agammann]

The output directory sets where files are written; Vite's top-level base sets the URLs written into the bundle. If your Go server exposes the generated build/ directory at /build/, add base: '/build/' alongside plugins and build in your existing vite.config.ts. See public base path.

I reproduced this with Vite 8.3.3 using a JS entry and an emitted image: the default base made build/build.js request /assets/image-...svg; base: '/build/' made it request /build/assets/image-...svg, matching the emitted file. You can keep index.html for development and your custom build input for the Go-served bundle.

[Icaro0310]

I keep index.html for vite dev, but for production I override the Rollup input so the build starts from the TSX file:

export default defineConfig({
 build: {
 manifest: true
 rollupOptions: {
 input: 'src/index.tsx'
 }
 }
})

That emits hashed JS/CSS assets without needing index.html as the build entry. On recent versions the manifest lands in dist/.vite/manifest.json, and my backend reads that file to serve the right asset names. I wouldn't use lib mode for a normal SPA bundle.

—
Related work of mine: github.com/Icaro0310 · Website: icaro0310.github.io