@vonage/vivid-bindings-vue NPM

vivid-bindings-vue

Typescript bindings for Vivid 3 web components to be used with VueJS 3

What's in the box(i.e. batteries included):

Few lines of code convergent initialization routine for Vivid design system
100% Vivid components covered with bindings
~100% automated process for NPM package generation & release. @vonage/vivid package is the release driver/trigger
Enhanced DevEx (VS Code intellisense) + Fully sound Typescript type checking for Vivid web components props/events/slots/cssProps/cssParts/etc. contracts
Abstraction layer for easier migration to future major versions of Vivid

How to integrate with VueJs App

Vivid can be initialized as easy as few lines of code

main.ts

import { createApp } from 'vue'
import App from './App.vue'
import { vivid3 } from '@vonage/vivid-bindings-vue'

const app = createApp(App)
app.use(vivid3, {
  font: 'oss',
  theme: 'dark'
})
app.mount('#app')

vite.config.ts

import { isCustomElement } from '@vonage/vivid-bindings-vue'

...

  plugins: [
    vue(
      {
        template: {
          compilerOptions: {
            isCustomElement
          },
        },
      }
    )
  ]

...

How to import components

Each Vivid component should be imported using single import statement. The Vivid major version is a part of the import v3. This enables seamless side by side usage of different major versions in a single project for pay as you go future migration path

<script setup lang="ts">
import { Connotation } from '@vonage/vivid'
import VwcButton from '@vonage/vivid-bindings-vue/v3/VwcButton'
import VwcIcon from '@vonage/vivid-bindings-vue/v3/VwcIcon'

function handleClick(e:PointerEvent) {}
</script>

<template>
  <VwcButton
     iconTrailing
     icon="github-mono"
     @click="handleClick"
     appearance='filled'
     label="I'm a Vivid button" />
  <VwcIcon
     name="key-solid"
     :connotation=Connotation.Alert
     :size=5 />
</template>

Releases

This package has a pipeline workflow which is checking for a new Vivid version on a dayly basis and if it detects that new version is out The new bindings are generated and published automatically, reflecting the same package version @vonage/vivid has. So the release driver is @vonage/vivid package itself.

Repository structure

The entire repository is a pure Typescript code, divided onto two main parts

./src - is the Deno territory, contains the generator code, which is effectively generates the NPM package contents on top of the existing template
./package - is the NPM package template

Rationale

Vivid web components since version 3.0 are shipped with the custom elements meta data alongside the code itself. Which allows to employ code generation practice to build near 100% automated typescript type safe bindings for VueJs components
Maintenance cost should be linear, it's always one component to be rendered, no matter how many elements there are actually in Vivid design system
Adds an abstraction layer to mitigate the custom web components namespacing conflicts issue, to enable usage of several major versions of Vivid components in the single application more info here, and how Salesforce Lightning web components are solving that issue here