@pollora/vite-config

The Vite configuration shared by Pollora themes, plugins and modules: where each one builds, its hot file, a dev server that works inside DDEV or Docker, its Gutenberg blocks, Tailwind CSS v4 and a page reload on Blade changes.

// vite.config.js
import { defineConfig } from 'vite';
import pollora from '@pollora/vite-config';

export default defineConfig({
    plugins: [pollora({ type: 'module' })],
});

It is a dev dependency of each theme, plugin or module, like laravel-vite-plugin. Nothing is shared at build time: each package keeps its own package.json, build and hot file, and pins its own version.

What type sets

type	Build directory (served by the framework)	Hot file	Default port	Extra
theme	public/build/theme/<name>	public/<name>.hot	5173	theme.json generated from the @theme tokens (wordpressThemeJson)
plugin	public/build/plugin/<name>	public/<name>.hot	5174	Page reload on .php changes
module	public/build/module/<kebab-name>	public/<kebab-name>.hot	5175	Page reload on .php changes

<name> is the directory name (Modules/BlocksDemo → blocks-demo for a module).

A classic theme, a plugin or a Bedrock site

Outside a Pollora project there is no shared public/ directory to build into. layout: 'standalone' builds the package inside itself, where pollora/assets looks for it:

// wp-content/themes/my-theme/vite.config.js, or web/app/themes/my-theme/vite.config.js
import { defineConfig } from 'vite';
import pollora from '@pollora/vite-config';

export default defineConfig({
    plugins: [pollora({ type: 'theme', layout: 'standalone' })],
});

	layout: 'pollora' (default)	layout: 'standalone'
Build	public/build/<type>/<name>/	build/ in the package
Hot file	public/<name>.hot	hot at the root of the package
base (URLs in the built CSS and chunks)	/build/<type>/<name>/	./: relative, so the build works wherever WordPress serves the folder from
Dev server	serves under the build path	serves from its root: the hot file holds the origin (http://localhost:5173)
Entry points	resources/assets/app.js, blocks	the same

buildDirectory (build) and hotFile (hot) rename the two, and publicDirectory (.) moves the folder they sit in; give the same values to the container on the PHP side (build_directory, hot_file, public_path). The manifest keys do not change (resources/assets/app.js), so a file is looked up the same way in both layouts.

Options

Option	Default
type	required	theme, plugin or module
name	directory name	Name the build is served under
input	resources/assets/app.js when it exists	Entries besides blocks
blocks	true	Build resources/views/blocks/*/{index,view}.{js,jsx,ts,tsx} and {editor,style}.css, and add @roots/vite-plugin's wordpressPlugin
tailwind	true	Add @tailwindcss/vite
themeJson	{ baseThemeJsonPath: './theme.json' }	Options for wordpressThemeJson (themes), or false
wordpress	{}	Options for wordpressPlugin
layout	'pollora'	'pollora' (a Pollora project) or 'standalone' (a classic theme, a plugin, Bedrock)
publicDirectory	the type's directory in a Pollora project, . when standalone	The public directory the build and hot file sit in, relative to the package root
buildDirectory	build (standalone only)	Build directory, relative to the public directory
hotFile	hot (standalone only)	Hot file, relative to the public directory
port	VITE_PORT, else the type's port	Dev server port
refresh	[]	Extra paths that reload the page
reloadOn	theme: ['.blade.php'], plugin and module: ['.blade.php', '.php']	File endings whose change reloads the page (a block theme adds .html)
assets	theme: resources/assets/{images,fonts}/**	Static assets copied to the build
publicDirectory	the project's public/, relative to the package
root	working directory	Package root

Requirements

Node 20.19+, vite 7 or 8, laravel-vite-plugin 2 or 3. @tailwindcss/vite and @roots/vite-plugin are needed when Tailwind CSS, blocks or theme.json generation are on.

License

MIT, © RuBee group.