@nextcloud/vite-config

Shared Vite ⚡ config for Nextcloud apps and libraries, which also can be easily extended.

API reference

The full API reference can be found on the documentation.

How to use

If your app uses an entry point for the main app and one for the settings page, then your default project tree will look like this:

css/
js/
lib/
src/
  |- ...
  |- main.js
  |- settings.js
package.json
vite.config.js

And your vite.config.js should look like this:

import { createAppConfig } from '@nextcloud/vite-config'

export default createAppConfig({
    // entry points: {name: script}
    main: 'src/main.js',
    settings: 'src/settings.js',
})

You can also modify the configuration, for example if you want to set an include path for the scss preprocessor:

import { createAppConfig } from '@nextcloud/vite-config'
import { defineConfig } from 'vite'
import path from 'node:path'

const yourOverrides = defineConfig({
    css: {
        preprocessorOptions: {
            scss: {
                includePaths: [
                    path.resolve(__dirname, './src/assets'),
                ],
            },
        },
    }
})

export default createAppConfig({
    // entry points
    main: 'src/main.js',
    settings: 'src/settings.js',
}, {
    // options
    config: yourOverrides
})

Use with a library

There is also a configuration for libraries, this configuration will handle the output directory correctly and automatically mark all dependencies as external:

import { createLibConfig } from '@nextcloud/vite-config'

const translations = //...

export default createLibConfig({
    index: 'src/index.js',
}, {
    replace: {
        TRANSLATIONS: translations,
    },
})

Notes

Inlining / injecting CSS

You can enable inlining CSS code, but please note that this is handled differently for apps and libraries.

• Apps will inline the CSS by dynamically inject it as script tags
• Libraries will extract the CSS to the dist/assets directory and import it in the entry point

For apps any styles can be injected in the JS by dynamically inject the styles in the document (creating <style> tags). But this only works in DOM environments, so for libraries this might not work (e.g. while testing in the Node environment).

So for libraries the CSS will still be extracted by Vite, but the extracted CSS assets will be imported. This way the library user can decide how to handle the imported CSS without relying on a DOM environment.