Awesome
TYPO3 Vite Plugin
This vite plugin collects entrypoints from TYPO3 extensions in a composer-based TYPO3 setup.
Installation
npm install --save-dev vite-plugin-typo3
This plugin is intended to be used together with vite_asset_collector.
Setup
Setup vite in your TYPO3 project:
vite.config.js:
import { defineConfig } from "vite";
import typo3 from "vite-plugin-typo3";
export default defineConfig({
plugins: [typo3()],
});
Provide entrypoints from an installed TYPO3 extension:
EXT:my_extension/Configuration/ViteEntrypoints.json:
[
"../Resources/Private/JavaScript/Main.entry.js",
"../Resources/Private/Entrypoints/*.entry.js"
]
Wildcards are possible, relative paths are relative to the location of the json file.
Configuration
Vite Configuration
The plugin tries to be as unintrusive as possible by only setting configuration values if they haven't been set already by the user. For example, if you want to use a custom manifest file name, you can set it as usual in your vite.config.js:
export default defineConfig({
plugins: [typo3()],
build: {
manifest: ".vite/custom-manifest-name.json",
},
});
Plugin Configuration
You can provide additional configuration to the plugin, for example:
plugins: [typo3({ debug: true })],
target
(string, defaultproject
): If set toextension
, vite can be used to bundle asset files for a singular TYPO3 extension. By default, they will be put intoResources/Public/Vite/
and retain their original file names. For JS files, both ESM and CJS variants will be generated. This mode can only be used withvite build
, not with the dev server.debug
(boolean, defaultfalse
): Show TYPO3-related debugging information in vite's cli outputentrypointFile
(string, defaultConfiguration/ViteEntrypoints.json
): Use a different file to provide entrypoints from extensions.entrypointIgnorePatterns
(array, default:["**/node_modules/**", "**/.git/**"]
): Files that should be ignored when using wildcards inViteEntrypoints.json
.