Provides debug and build capabilities for pilets and Piral instances using Vite.
npm install piral-cli-vite
This plugin enables using Vite as the bundler for Piral instances and pilets.
Use your favorite npm client for the installation:
``sh`
npm i piral-cli-vite --save-dev
Note: If you don't install any bundler for use in piral-cli then piral-cli-vite will be automatically installed for you.
There is nothing to do. Standard commands such as piral build or pilet debug will now work with Vite as the bundler.
This plugin comes with batteries included. You don't need to install or specify your Vite version.
Right now it includes:
- vite-plugin-codegenvite-plugin-environment
-
Additionally, most known referenced assets are handled as files.
As such it should be prepared to include assets (images, videos, ...), stylesheets (CSS and SASS), and work with TypeScript.
By default the source folder (e.g., /src) is set as root. Therefore, the src/public folder (if available) will be used for the public assets. If you want to change this you can use a custom Vite config as explained below, e.g.:
`js
import { resolve } from 'path';
export default {
publicDir: resolve(__dirname, 'public'),
}
`
Vite uses all scripts with type=module to be entry points in the index.html file. However, as you might just have scaffolded a solution or are more used to simply have
`
to
`html`
If you want to customize the given config (e.g., to add more plugins) then create a file vite.config.js (or anything else accepted by Vite, e.g., vite.config.ts) in your root directory.
In the most trivial version the file looks as follows:
`js
import { defineConfig } from 'vite';
export default defineConfig({
// Your config additions here
});
`
If you want to add some plugin you could do:
`js
import { defineConfig } from "vite";
import legacy from "@vitejs/plugin-legacy";
export default defineConfig({
plugins: [
legacy({
targets: ['defaults', 'not IE 11'],
}),
],
});
``
The configuration works with all formats that Vite supports.
Piral is released using the MIT license. For more information see the license file.