@pitchfork-ui/elements-vue
| Install | |
|---|---|
npm install @pitchfork-ui/elements-vue |
|
| Latest Version: | 0.2.1 |
| Vue: | 3 |
| License: | MIT |
| Last Updated: | Oct 21, 2026 |
| Links: | GitHub · npm |
@pitchfork-ui/elements-vue
Vue bindings for @pitchfork-ui/elements —
typed Vue components generated from the Pitchfork UI custom elements.
Vue can render custom elements directly, so these bindings are a convenience
rather than a necessity. What they add is worth having: typed props, events
exposed as @pf-* listeners rather than addEventListener, and v-model
support on the form controls.
Install
npm install @pitchfork-ui/elements-vue @pitchfork-ui/tokens
Use
<script setup lang="ts">
import { PfButton, PfInput } from '@pitchfork-ui/elements-vue';
import { ref } from 'vue';
const email = ref('');
</script>
<template>
<PfInput v-model="email" label="Email" name="email" />
<PfButton variant="primary">Save</PfButton>
</template>
Load the token stylesheet once, at the root of your application:
import '@pitchfork-ui/tokens/css';
v-model works on pf-input, pf-textarea, pf-radio-group, pf-slider,
pf-checkbox and pf-switch — the same six controls that have an Angular
ControlValueAccessor, bound the same way. A checkbox and a switch model
their checked; the others model their value.
Generated, not hand-written
Every file under src/components/ is produced by the Stencil Vue output
target when @pitchfork-ui/elements builds. Fix anything wrong with a wrapper
in the element it comes from, not here.
Licence
MIT
Related Packages
Framework-agnostic custom elements for Pitchfork UI — the design system as stand...
Framework-agnostic custom elements for the Kanso Protocol design system — use co...
Open-source CLI for measuring design-system component usage across multi-framewo...
Version History
| Version | Released | Vue | License |
|---|---|---|---|
| 0.2.1 | >=3.4.38 | MIT | |
| 0.1.0 | >=3.4.38 | MIT |
Pre-releases (1)
| Version | Released | License |
|---|---|---|
| 0.0.0-stage |