Transforming full-fledged Vue3 applications into reusable web components
vue-web-component-wrapper is a powerful Vue 3 plugin designed for transforming full-fledged Vue applications into reusable web components (custom elements). These web components can be integrated into any website, enhancing flexibility and reusability.
As of now, Vue 3 does not support the creation of full applications as web components out of the box. This plugin aims to solve this problem by providing a simple and easy-to-use solution for creating web components from Vue applications. It also provides support for Vue ecosystem plugins such as Vuex, Pinia, Vue Router, Vue I18n, and VeeValidate.
Check out these demo projects to see vue-web-component-wrapper in action:
- Webpack implementation: Check out this Webpack Demo Project
- Vite.js implementation: Check out this Vite Demo Project
See Docs
- Vue Plugins Compatibility: Seamlessly integrates with Vue ecosystem plugins such as Vuex, Vue Router, and Vue I18n.
- CSS Framework Support: Works with popular CSS frameworks like Tailwind CSS, Bootstrap, Vuetify, Element Plus, and more.
- CSS Preprocessor Support: Allows you to use CSS preprocessors like SCSS and LESS.
- Scoped CSS: Allows you to use scoped CSS in your components.
- Shadow DOM Support: Facilitates the encapsulation of styles and scripts for your components, preventing clashes with the rest of your application.
- VUE Devtool Support: Supports the Vue DevTools browser extension.
- Slot and Named Slot Support: Define and use slots and named slots within web components.
- v-model Support: Improved support for two-way data binding using
v-modelarchitecture. - Event Emitting Support: Emit and handle custom events from web components.
- Provide/Inject Support: Pass data from parent to child components using
provideandinject. - Disable Removal of Styles on Unmount: Control the removal of styles upon component unmount, which can solve issues with CSS transitions.
- Disable Shadow DOM: Disable Shadow DOM for web components.
- Replace
:rootwith:host: Optionally replace:rootselectors with:hostin your CSS to ensure styles are correctly scoped within the Shadow DOM.
See documentation for more details Docs
npm install vue-web-component-wrapper
# or
yarn add vue-web-component-wrapper
# or
pnpm add vue-web-component-wrapperTo create a web component using vue-web-component-wrapper, follow the steps below:
- Import the necessary modules in your entry file:
import App from './App.vue';
import tailwindStyles from './assets/tailwind.css?raw';
import { createWebHashHistory, createRouter } from 'vue-router';
import { createI18n } from 'vue-i18n';
import { createStore } from 'vuex';
import { createPinia } from 'pinia';
import { defaultRoutes } from './main.routes.js';
import { store } from './store/index.js';
import { defineCustomElement as VueDefineCustomElement, h, createApp, getCurrentInstance } from 'vue';
import { createWebComponent } from 'vue-web-component-wrapper';- Set up the instances and use your plugins. This is where you configure your Vuex/Pinia store, Vue Router, and other Vue plugins.
export const pluginsWrapper = {
install(GivenVue) {
const Vue = GivenVue;
// Vuex
const createdStore = createStore(store);
Vue.use(createdStore);
// or Pinia
const pinia = createPinia();
Vue.use(pinia);
// Vue Router
const router = createRouter({
history: createWebHashHistory(),
routes: defaultRoutes,
});
Vue.use(router);
// Vue I18n
const i18n = createI18n({
locale: 'en',
fallbackLocale: 'en',
});
Vue.use(i18n);
},
};- Create your web component using
createWebComponent. It takes an options object where you specify your root Vue component, the element name for your custom element, any plugins you want to use, and any CSS framework styles.
createWebComponent({
rootComponent: App,
elementName: 'my-web-component',
plugins: pluginsWrapper,
cssFrameworkStyles: tailwindStyles,
VueDefineCustomElement,
h,
createApp,
getCurrentInstance,
disableStyleRemoval: false, // default is false
disableShadowDOM: false, // default is false
replaceRootWithHost: false, // default is false
});Each option in the createWebComponent function has a specific purpose:
rootComponent: The root component of your Vue application.elementName: The tag name for your custom web component. It must contain a hyphen and be lowercase.plugins: Any Vue plugins you want to use in your application.cssFrameworkStyles: Any CSS or SCSS styles that your application needs.VueDefineCustomElement: ThedefineCustomElementfunction from Vue.h: Thehfunction from Vue.createApp: ThecreateAppfunction from Vue.getCurrentInstance: ThegetCurrentInstancefunction from Vue.disableStyleRemoval: Boolean to disable removal of styles on unmount, which can solve issues with CSS transitions.disableShadowDOM: Boolean to disable Shadow DOM for web components.replaceRootWithHost: New Feature (defaultfalse). Boolean to replace:rootselectors with:hostin your CSS styles.
The replaceRootWithHost option allows you to replace all occurrences of :root with :host in your cssFrameworkStyles. This is particularly useful when working with CSS variables defined on :root, ensuring they are properly scoped within the Shadow DOM of your web component.
createWebComponent({
rootComponent: App,
elementName: 'my-web-component',
plugins: pluginsWrapper,
cssFrameworkStyles: tailwindStyles,
VueDefineCustomElement,
h,
createApp,
getCurrentInstance,
replaceRootWithHost: true,
});The cssFrameworkStyles option is used to import the CSS of your CSS framework or any other CSS styles that your application needs to have globally. This option can also handle CSS variables that are defined on a :root selector.
By setting replaceRootWithHost to true, any :root selectors in your CSS framework styles will be replaced with :host. This ensures that styles and CSS variables are correctly scoped to the web component, preventing unintended style leakage or conflicts with the parent document.
In some cases, you might want to use CSS variables defined in :root that penetrate the Shadow DOM. To achieve this, you need to import the CSS variables to the host of the web component.
- Build your application. Tested bundler to build the web-component application.
Vite Configuration
Here's a sample Vite configuration. Comparing with Webpack, Vite.js is able to handle asset files like .css and .scss, and media files, importing them as you do regularly. Vue files will be parsed using the official @vitejs/plugin-vue depending on config. If you would like to add plugins for Vite, just install them with your favorite Node package manager.
import { defineConfig } from 'vite';
import vue from '@vitejs/plugin-vue';
export default defineConfig({
build: {
sourcemap: 'inline',
},
plugins: [
vue({
customElement: true,
}),
],
});In your main.js/ts file, you will have to import the CSS framework in a slightly different way than Webpack with ?inline at the end of the import statement. This leads to a new issue with fonts, which are not loaded when using ?inline. To fix this, you can import the font CSS in the App.vue file.
// ?inline cannot handle import url() in CSS; therefore, fonts are not loaded. Workaround is to add font CSS to the App.vue
import style from './style.css?inline';Workaround for fonts:
<style>
@import url('https://fonts.googleapis.com/css2?family=YourFont');
header {
@apply font-sans;
}
main {
@apply font-sans;
}
</style>Webpack Configuration
Here's a sample webpack configuration that helps webpack understand how to load and process .vue, .css, and .scss files. It also sets up an HTML plugin for webpack.
const path = require('path');
const { VueLoaderPlugin } = require('vue-loader');
const HtmlWebpackPlugin = require('html-webpack-plugin');
module.exports = {
mode: 'production',
entry: './src/main.js',
output: {
path: path.resolve(__dirname, 'dist'),
filename: 'my-web-component.js',
},
module: {
rules: [
{
test: /\.(vue|ce\.vue)$/,
loader: 'vue-loader',
options: {
customElement: true,
},
},
{
test: /\.(css|scss)$/,
oneOf: [
{
resourceQuery: /raw/,
use: [
'to-string-loader',
'css-loader',
'postcss-loader',
{
loader: 'sass-loader',
options: {
sassOptions: {
indentedSyntax: false, // Use the SCSS syntax
},
},
},
],
},
{
use: [
'style-loader',
'css-loader',
'postcss-loader',
{
loader: 'sass-loader',
options: {
sassOptions: {
indentedSyntax: false, // Use the SCSS syntax
},
},
},
],
},
],
},
{
test: /\.(png|jpe?g|gif|svg)(\?.*)?$/,
loader: 'file-loader',
options: {
name: 'assets/[name].[hash:7].[ext]',
},
},
],
},
plugins: [
new VueLoaderPlugin(),
new HtmlWebpackPlugin({
template: './public/index.html',
}),
],
resolve: {
alias: {
vue$: 'vue/dist/vue.esm-bundler.js',
},
extensions: ['.js', '.vue', '.json'],
},
};With webpack, you will have to import the CSS framework in a slightly different way than Vite with ?raw at the end of the import statement.
import style from './style.css?raw';If you want to create a web component without Shadow DOM, you can set the disableShadowDOM option to true in the createWebComponent function. This will create a web component without Shadow DOM encapsulation.
This feature uses a patch to the Vue source code, which could lead to some issues with future versions of Vue. If you encounter any issues, please report them in the issues section of this repository.
Enhance the core functionality of Single File Components (SFC) as Custom Elements defineCustomElement with two new features:
- Nested Components: You can use nested components with styles and, for example, share base components between multiple custom elements.
- Shadow DOM Option: You can disable Shadow DOM for the SFC custom element.
// main.js
import { defineCustomElementSFC } from 'vue-web-component-wrapper';
const MyComponentElement = defineCustomElementSFC(MyComponent, { shadowRoot: false });
customElements.define('my-component', MyComponentElement);- Testing Production Build: The easiest way to test your production build is to run a local server in the
distfolder. You can use valet for this, but any local server should work.
- TypeScript Support: Adding proper strict types.
Contributions are welcome! To contribute to the project, please follow these steps:
- Fork the repository
- Create a new branch for your feature or bug fix
- Make your changes and commit them with a clear message
- Push your changes to your fork
- Submit a pull request to the main repository
Please make sure to follow the code style and conventions used in the project.
If you find a bug or have a feature request, please open an issue on the repository.
This project is licensed under the MIT License.