Package Exports
- @sveltejs/vite-plugin-svelte
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (@sveltejs/vite-plugin-svelte) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
@sveltejs/vite-plugin-svelte
usage
// vite.config.js
const svelte = require('@sveltejs/vite-plugin-svelte');
const { defineConfig } = require('vite');
module.exports = defineConfig(({ command, mode }) => {
const isProduction = mode === 'production';
return {
plugins: [
svelte({
/* inline options here */
})
],
build: {
minify: isProduction
}
};
});Options
vite-plugin-svelte reads the vite configuration and uses an appropriate default configuration
It also loads svelte.config.js (or svelte.config.cjs) from the configured vite.root directory automatically.
Options are applied in the following order:
- vite-plugin-svelte defaults
- svelte.config.js in vite.root
- inline options passed in vite.config.js
It supports all options from rollup-plugin-svelte and some additional options to tailor the plugin to your needs.
For more Information check options.ts
Integrations for other vite plugins
Add an extra preprocessor
vite-plugin-svelte uses the svelte compiler to split .svelte files into js and css and the svelte compiler requires that the css passed to it is already plain css.
If you are building a plugin for vite that transforms css and want it to work out of the box with vite-plugin-svelte, you can add a sveltePreprocess: PreprocessorGroup to your vite plugin definition and vite-plugin-svelte will pick it up and add it to the list of svelte preprocessors used at runtime.
const vitePluginCoolCss = {
name: 'vite-plugin-coolcss',
sveltePreprocess: {
/* your PreprocessorGroup here */
}
/*... your cool css plugin implementation here .. */
};Check out windicss
License
MIT