Note that only attribute values that are static strings are transformed. Otherwise, you'd need to import the asset manually, e.g. import imgUrl from '../image.png'.
import vue from '@vitejs/plugin-vue'import yaml from 'js-yaml'const vueI18nPlugin = { name: 'vue-i18n', transform(code, id) { // if .vue file don't have <i18n> block, just return if (!/vue&type=i18n/.test(id)) { return } // parse yaml if (/\.ya?ml$/.test(id)) { code = JSON.stringify(yaml.load(code.trim())) } // mount the value on the i18n property of the component instance return `export default Comp => { Comp.i18n = ${code}
Create a file named Demo.vue, add lang="yaml" to the <i18n> blocks, then you can use the syntax of YAML:
Vue 3.2 introduces the defineCustomElement method, which works with SFCs. By default, <style> tags inside SFCs are extracted and merged into CSS files during build. However when shipping a library of custom elements, it may be desirable to inline the styles as JavaScript strings and inject them into the custom elements' shadow root instead.
Starting in 1.4.0, files ending with *.ce.vue will be compiled in "custom elements" mode: its <style> tags are compiled into inlined CSS strings and attached to the component as its styles property:
import { defineCustomElement } from 'vue'import Example from './Example.ce.vue'console.log(Example.styles) // ['/* css content */']// registercustomElements.define('my-example', defineCustomElement(Example))
Note in custom elements mode there is no need to use <style scoped> since the CSS is already scoped inside the shadow DOM.
The customElement plugin option can be used to configure the behavior:
{ customElement: true } will import all *.vue files in custom element mode.
Use a string or regex pattern to change how files should be loaded as Custom Elements (this check is applied after include and exclude matches).
License
MIT
vitebot
vite@voidzero.dev
* - `string | RegExp`: matched files are converted into custom elements