Files
inbuxa-admin/vite.config.ts
T
jcoffey-dev 63df3d572d
ci / build (pull_request) Skipped
ci / publish (pull_request) Skipped
ci / notices (pull_request) Successful in 53s
github/ci (branch) GitHub Actions
ci / github (pull_request) Successful in 2m2s
Version 27.1-rc.1: the suite's series versions
inbuxa-version.json is now 27.1-rc.1, the version the whole suite moves to.
The console shows just that: the "(base 1.0.11)" suffix named the release
the fork started from, and no upstream version is shown any more.

tools/release-version.sh holds the rule (POSIX sh, for the docker:cli
image): a release moves its series tag and :latest; a release candidate
its series' -rc tag, never :latest. Both CIs publish v27.1, v27.1.N and
v27.1-rc.N tags as well as the dated ones from before.

The weekly release cuts the next patch of the series (27.1 -> 27.1.1),
and while main is on a release candidate it says so and stops: a series
and its candidates are cut by hand.
2026-10-28 09:35:15 -07:00

29 lines
1.0 KiB
TypeScript

// SPDX-FileCopyrightText: 2026 Coffey Labs LLC
// SPDX-License-Identifier: AGPL-3.0-only
// defineConfig from vitest/config, not vite, so the `test` section is typed.
import tailwindcss from '@tailwindcss/vite'
import react from '@vitejs/plugin-react'
import path from 'path'
import { configDefaults, defineConfig } from 'vitest/config'
import inbuxa from './inbuxa-version.json' with { type: 'json' }
import { sievePlayground } from './sieve-playground.ts'
export default defineConfig({
// Relative, so one build works at any mount point (/admin, /account).
base: './',
define: {
// The release version as tags name it (27.1, 27.1.3, 27.1-rc.1). Only
// inbuxa's: package.json's is a leftover nothing shows.
__APP_VERSION__: JSON.stringify(inbuxa.version),
},
plugins: [react(), tailwindcss(), sievePlayground()],
resolve: { alias: { '@': path.resolve(import.meta.dirname, './src') } },
test: {
environment: 'happy-dom',
globals: false,
exclude: [...configDefaults.exclude, '**/.ignore/**'],
},
})