Skip to content

Quick start ​

Verify one plugin first ​

Put this configuration in vite.config.ts in a Vite application with the package installed. If you already have a configuration, append buildInfo(...) to its plugins array.

ts
import { defineConfig } from "vite";
import { buildInfo } from "fast-vite-plugins";

export default defineConfig({
	plugins: [buildInfo({ fileName: "meta/build-info.json" })],
});

Run pnpm exec vite build. With the default output directory, dist/meta/build-info.json contains version, builtAt and mode. If your project sets build.outDir, look for meta/build-info.json in that directory.

Combine plugins ​

Built-in SDK errors and warning diagnostics use English, retaining the [fast-vite:plugin-name] prefix and relevant configuration or path context. Caller-provided validation messages and underlying errors remain unchanged. The language change does not affect error types, triggering conditions, or the error / warn policy.

ts
import { defineConfig } from "vite";

import { buildInfo, bundleBudget, compression, envGuard, subresourceIntegrity } from "fast-vite-plugins";

export default defineConfig({
	plugins: [
		envGuard({
			schema: { VITE_API_URL: { pattern: /^https:\/\// } },
		}),
		buildInfo(),
		subresourceIntegrity({ manifest: true }),
		bundleBudget({
			budgets: [
				{ name: "entry JavaScript", filter: /\.js$/, limit: 250 * 1024 },
				{ name: "all CSS (gzip)", filter: /\.css$/, limit: 50 * 1024, mode: "gzip", scope: "total" },
			],
		}),
		compression({ algorithms: ["gzip", "brotli"], threshold: 10 * 1024 }),
	],
});

Every plugin is imported and configured independently. The package does not enable implicit behavior.

ts
import { defineConfig } from "vite";
import { buildInfo, htmlTemplate } from "fast-vite-plugins";

export default defineConfig({
	plugins: [htmlTemplate({ data: { APP_TITLE: "Fast Admin" }, strict: true }), buildInfo({ fileName: "meta/build-info.json" })],
});

Build completes but the build-info file is missing ​

Confirm that the build is using a configuration that registers buildInfo. Look in the configured output directory using fileName. With fileName: "meta/build-info.json", the file is in its meta/ subdirectory. See more recipes.