Overview of official Vituum plugins for Vite
build.rollupOptions.input if used without Vituum's multi-page support.website·Indexed 32 days ago
https://vituum.dev/A collection of plugins for Vite that adds additional features such as multi-page support and various template engines. Supported engines and plugins include Handlebars, Liquid, Nunjucks, Pug, Twig, Latte, PostHTML, PostCSS, TailwindCSS, and Juice.
build.rollupOptions.input if used without Vituum's multi-page support.Vituum 1.0 is a complete rewrite where the core is now a Vite plugin rather than a wrapper around Vite. Key changes include:
plugins array in the config.@vituum/vite-plugin-postcss to add it.src/views directory has been renamed to src/pages (this can be customized in the config).vituum build command is removed; build directly using Vite.<script type="application/json"> is removed. Use dedicated template files (e.g., .liquid, .pug, .json).// 0.0.X Configuration
import { defineConfig } from 'vituum'
import liquid from '@vituum/liquid'
export default defineConfig({
integrations: [liquid()],
templates: {
format: 'liquid'
}
})
// 1.0.0 Configuration
import vituum from 'vituum'
import liquid from '@vituum/vite-plugin-liquid'
export default {
plugins: [vituum(), liquid()]
}Vituum supports several template engines via plugins, which can be used independently or with the Vituum core plugin for multi-page support in Vite. Supported engines include Liquid, Twig, Latte, Nunjucks, Pug, and Handlebars.
By default, pages are added in the pages directory, while templates and components are typically stored in layouts, components, or templates directories.
src/pages directory. This plugin applies to .html files and template files (e.g., .liquid, .twig, .json).npm i vituum --save-dev
# or
yarn add vituum -Dvituum plugin to your vite.config.js (or .mjs, .ts) file in the project root. You can use Vituum plugins independently if you do not require the core multi-page support features.import vituum from 'vituum'
export default {
plugins: [vituum()]
}# Using npm
npm i @vituum/vite-plugin-concat --save-dev
# Using yarn
yarn add @vituum/vite-plugin-concat -D# Using npm
npm i @vituum/vite-plugin-handlebars --save-dev
# Using yarn
yarn add @vituum/vite-plugin-handlebars -D# Using npm
npm i @vituum/vite-plugin-twig --save-dev
# Using yarn
yarn add @vituum/vite-plugin-twig -Dsend function independently of Vite by importing it from @vituum/vite-plugin-send/send.js. This is useful for creating custom npm scripts to trigger emails manually without using the ?send URL parameter. It accepts the same options as the Vite plugin.import { send } from '@vituum/vite-plugin-send/send.js'
// Use with the same options as the plugin
send({
to: 'user@example.com',
host: 'smtp.example.com',
// ... other options
}).css, .less, .scss, .js, and .ts files. By creating a file named +.css (or similar) in a directory, you can aggregate imports./* src/styles/Components/+.css */
@import "Button.css";
@import "Badge.css";
/* src/styles/main.css */
@import "Components/+.css";