Compile Svelte components.
npm install --save-dev rollup-plugin-svelte// rollup.config.js
import * as fs from 'fs';
import svelte from 'rollup-plugin-svelte';
export default {
entry: 'src/main.js',
dest: 'public/bundle.js',
format: 'iife',
plugins: [
svelte({
// By default, all .html and .svelte files are compiled
extensions: [ '.my-custom-extension' ],
// You can restrict which files are compiled
// using `include` and `exclude`
include: 'src/components/**/*.html',
// By default, the client-side compiler is used. You
// can also use the server-side rendering compiler
generate: 'ssr',
// Extract CSS into a separate file (recommended).
// See note below
css: function (css) {
console.log(css.code); // the concatenated CSS
console.log(css.map); // a sourcemap
// creates `main.css` and `main.css.map` — pass `false`
// as the second argument if you don't want the sourcemap
css.write('public/main.css');
}
})
]
}If you're importing a component from your node_modules folder, and that component's package.json has "svelte" and/or "svelte.root" properties...
{
"name": "some-component",
// this means 'some-component' resolves to 'some-component/src/SomeComponent.html'
"svelte": "src/MyComponent.html",
// this means 'my-component/Foo.html' resolves to 'some-component/src/Foo.html'
"svelte.root": "src"
}...then this plugin will ensure that your app imports the uncompiled component source code. That will result in a smaller, faster app (because code is deduplicated, and shared functions get optimized quicker), and makes it less likely that you'll run into bugs caused by your app using a different version of Svelte to the component.
Conversely, if you're publishing a component to npm, you should ship the uncompiled source (together with the compiled distributable, for people who aren't using Svelte elsewhere in their app) and include these properties in your package.json.
If your Svelte components contain <style> tags, by default the compiler will add JavaScript that injects those styles into the page when the component is rendered. That's not ideal, because it adds weight to your JavaScript, prevents styles from being fetched in parallel with your code, and can even cause CSP violations.
A better option is to extract the CSS into a separate file. Using the css option as shown above would cause a public/main.css file to be generated each time the bundle is built (or rebuilt, if you're using rollup-watch), with the normal scoping rules applied.
Alternatively, if you're handling styles in some other way and just want to prevent the CSS being added to your JavaScript bundle, use css: false.
MIT