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 🙏

© 2024 – Pkg Stats / Ryan Hefner

vue2-multiple-vmodels

v0.1.0

Published

A vue2 implementation for v-models and v-model object destructuring

Downloads

601

Readme

Vue2 Multipe V-Models

A multiple v-model implementation for Vue2

Read about it here in detail https://dev.to/michaelolof_/multiple-v-model-for-the-rest-of-us-1pb8


Installation

$ npm install --save vue2-multiple-vmodels

In main.js file

import Vue from "vue"
import Vue2MultipleVModels from "vue2-multiple-vmodels";

Vue.use(Vue2MultipleVModels);

API

The library comes with 2 helper directives.

  • v-models - Multiple 2 way binding for vue2
  • v-model-destruct - Destructure a v-model object and bind directly to its fields

v-models

The v-models directive gives you the power of multiple v-models just like in the new vue 3 feature. You can create a component that supports v-models like this

SelectInput.vue

<template>
  <div class="select-input">
    <select v-model="select" class="select-input__select">
      <slot />
    </select>
    <input v-model="input" class="select-input__input" />
  </div>
</template>

<script>
export default {
  models: [
    { data: "select", event: "models:select" },
    { data: "input", event: "models:input" },
  ],
  data() {
    return {
      select: undefined,
      input: "",
    }
  },
  watch: {
    select(newVal) {
      this.$emit("models:select", newVal);
    },
    input(newVal) {
      this.$emit("models:input", newVal);
    },
  },
}
</script>

This component can then be used like this

<template>
  <SelectInput v-models:input="amount" v-models:select="currency">
</template>

<script>
export default {
    data() {
        return {
            input: 100,
            currency: "GHS"
        }
    }
}
</script>

Caveats

  • Only works with custom components.
  • v-models relies on data not props. Props can still be used to sync data the traditional way, but we register the data and the event not the prop
  • All v-models events must be of the format with models:<xxx> The v-models directive checks for this.
  • Registeration of data and event is done in the models section when defining the component. models must be an array.

v-model-destruct

Use full for existing/already defined components which emit objects.

Take a PhoneCountry component which emits an object as shown below PhoneCountry.vue

<template>
  <PhoneCountry v-model="phone">
</template>

<script>
export default {
  data() {
      return {
          phone: {
              country: "Nigeria",
              dial: "234",
              phone: "234123456789"
          }
      }
  }
}
</script>

v-model-destruct allows you bind (2-way binding) directly to any of the fields you're interested in. E.g

<template>
  <PhoneCountry v-model-destruct:country="country" v-model-destruct:phone="phone" />
</template>

<script>
export default {
    data() {
        return {
            country: "Nigeria",
            phone: "234123456789"
        }
    }
}
</script>

Caveats

  • Only works with Components that emit objects or the value of v-model is an object.
  • 2-way binding is limited to component design. If your component (E.g PhoneCountry) is not designed to track changes in object fields (E.g country field), changes made when you update country from the parent component might not update the child (PhoneCountry) component.