import { defineConfig } from 'vite';

// Builds resources/css/all.css alone, with no other plugin in the graph: it isolates Vite's own
// bundled postcss-import, whose `skipDuplicates` option is the mechanism
// docs/plans/material-3-alignment.md's "Tailwind's footprint" paragraph measured and
// StylesheetsBundleTest.php pins against the real bundler — a stylesheet several files import
// lands once, at its first position.
//
// The Workbench's own entry (vite.config.js) still shares one file with `@tailwindcss/vite` until
// plan step 39 removes it, and that plugin bundles its whole reachable module graph itself,
// independently of Vite's CSS pipeline; it does not carry the same `skipDuplicates` option, so a
// shared component stylesheet currently lands once per import site there, not once overall. That
// is a pre-existing limitation of mixing the two in one entry, not something plan step 37
// introduces or can fix without moving Tailwind out of the Workbench's entry (step 39's job) — this
// fixture is what actually exercises the claim being pinned, decoupled from it.
export default defineConfig({
    build: {
        outDir: process.env.DEDUP_OUT_DIR,
        emptyOutDir: true,
        manifest: true,
        rollupOptions: {
            input: 'resources/css/all.css',
        },
    },
    logLevel: 'silent',
});