npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@xplortech/apollo-vue

v2.8.1

Published

Vue bindings for Apollo design system web components

Readme

Apollo Vue

Vue 3 bindings for the Apollo design system (@xplortech/apollo-core web components). Use this package in Vue apps for props, events, and v-model on form controls.

Installation

Published as @xplortech/apollo-vue on the public npm registry (same scope as @xplortech/apollo-core and @xplortech/apollo-react).

npm install @xplortech/apollo-vue @xplortech/apollo-core

Peer dependencies: Vue 3+ and TypeScript 5+.

Import styles once in your app (path may vary with your bundler):

import '@xplortech/apollo-vue/css/apollo.css';

Registering components

Option A — global plugin (registers custom elements)

import { createApp } from 'vue';
import { ComponentLibrary } from '@xplortech/apollo-vue';
import App from './App.vue';

const app = createApp(App);
app.use(ComponentLibrary);
app.mount('#app');

Option B — import only what you use

<script setup lang="ts">
import { XplButton, XplInput } from '@xplortech/apollo-vue';
</script>

<template>
  <XplButton variant="primary">Save</XplButton>
  <XplInput v-model="email" label="Email" type="email" />
</template>

Importing from @xplortech/apollo-vue loads the generated proxies, which call defineCustomElements() from @xplortech/apollo-core/loader.

v-model (form components)

These wrappers map v-model to the correct property and update event:

| Component | v-model binds to | Update event (internal) | |---------------|--------------------|-------------------------| | XplInput | value | valueChange | | XplCheckbox | checked | checkboxChange | *| | XplRadio | checked | radioChange | | XplToggle | checked | toggleChange | | XplSelect | selectedValues | changeEvent |

Example:

<script setup lang="ts">
import { ref } from 'vue';
import { XplInput, XplCheckbox, XplSelect } from '@xplortech/apollo-vue';

const name = ref('');
const agreed = ref(false);
const selected = ref<string | string[]>([]);
</script>

<template>
  <XplInput v-model="name" label="Name" />
  <XplCheckbox v-model="agreed" label="I agree" />
  <XplSelect
    v-model="selected"
    label="Choose"
    :choices="[]"
    placeholder="Select…"
  />
</template>

* XplCheckbox v-model binds to checked. When no value prop is set, it emits a boolean (checked state). When value is also set, it emits the string value when checked. Type your ref accordingly.

XplChoicelist: there is no v-model mapping yet; use @choicelistChange / @choicelistValueChange and props manually.

Specialized input types: <XplInput type="date" />, type="time", type="phone", type="color", and type="file" all work with v-model. Internally, xpl-input renders a sub-component (e.g. xpl-input-date) and forwards its events. Prefer <XplInput type="date" v-model="val" /> over using XplInputDate directly.

Events and complex props

Stencil @Event() names are exposed as Vue emits (e.g. @valueChange, @checkboxChange). Pass objects and arrays as props the same way as with other Vue components:

<script setup lang="ts">
import { XplTable } from '@xplortech/apollo-vue';
const rows = [[]];
const cols = [];
function onSelect() {}
</script>

<template>
  <XplTable :data="rows" :columns="cols" @table-select="onSelect" />
</template>

Suppressing unknown-element warnings

If your bundler warns about xpl-* tags as unknown custom elements, tell the Vue compiler to treat them as web components:

// vite.config.ts
import vue from '@vitejs/plugin-vue';

export default {
  plugins: [
    vue({
      template: {
        compilerOptions: {
          isCustomElement: (tag) => tag.startsWith('xpl-'),
        },
      },
    }),
  ],
};

Further reading

  • Apollo repo
  • Core components and behavior: @xplortech/apollo-core / Storybook in this monorepo