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

vue-ref-name

v0.0.1

Published

reference .vue component by the refName

Readme

vue-ref-name

easy reference vue component by refName

Introduction

Sometimes we need to get data from other vue components or trigger the methods of another components.vue-ref-name make it easier. Of course there is vuex which is a more powerful state management tool,vue-ref-name is still another choice if you know what you did

Installation

$ npm install vue-ref-name

Example

// just install the vue-ref-nam via Vue.use()

import Vue from 'vue'
import refName from 'vue-ref-name'

vue.use(refName)     // and now your can use this.$refName.componentName to get the component with the name 'componentName'


// for example: we have document tree:

//main.vue
<template>
  <div id="app">
    <ComponentA/>
    <ComponentB/>
  </div>
</template>

<script>
import ComponentA from '.ComponentA.vue'
import ComponentB from '.ComponentB.vue'
export default {
  name: 'app',
  components: { ComponentA, ComponentB },
  data () {
    return {
      mainData: 'component main'
    }
  },
  mounted () {
    console.log(this.$refName.refA.infoA, this.$refName.refB.infoB)    // I am ComponentA, I am ComponentB
  }
}
</script>

// ComponentA.vue
<template>
  <p>{{infoA}}<p>
</template>
<script>
  name: 'refA',
  data () {
    return {
      infoA: 'I am ComponentA'
    }
  },
  mounted () {
    this.$refName.infoB.sayHello()   // will change infoB to "hello"
  }
</script>

// ComponentB.vue
<template>
  <p>{{infoB}}<p>
</template>
<script>
  name: 'refB',
  data () {
    return {
      infoB: 'I am ComponentB'
    }
  },
  methods: {
    sayHello () {
      console.log('will change infoB to "hello"')
      this.infoB = "hello"
    }
  }
</script>

The default config will look for attribute name of each vue component and registe to the refName, then we can get the instance via this.$refName.componentName.But there is a problem, if we re-use the same component,this.$refName.componentName can only get the first mounted one. So, it's recommend to make sure the name as uniquity. Todo that, we can define the refName:

import Vue from 'vue'
import refName from 'vue-ref-name'

vue.use(refName, {refName: 'refName'}) 

//main.vue
<template>
  <div id="app">
    <ComponentA/>
    <ComponentB :newName="'ComponentB1'"/>
    <ComponentB :newName="'ComponentB2'"/>
  </div>
</template>

<script>
import ComponentA from '.ComponentA.vue'
import ComponentB from '.ComponentB.vue'
export default {
  name: 'app',        // this.$refName.app is undefined
  refName: 'myApp',  // now this.$refName.myApp is activity
  components: { ComponentA, ComponentB },
  data () {
    return {
      mainData: 'component main'
    }
  },
  mounted () {
    console.log(this.$refName.myRefA.infoA)    // I am ComponentA
  }
}
</script>

// ComponentA.vue
<template>
  <p>{{infoA}}<p>
</template>
<script>
  name: 'refA',
  refName: 'myRefA',
  data () {
    return {
      infoA: 'I am ComponentA'
    }
  },
  mounted () {
    this.$refName.ComponentB1.sayHello()   // ComponentB1
    this.$refName.ComponentB2.sayHello()  //  ComponentB2
  }
</script>

// ComponentB.vue
<template>
  <p>{{infoB}}<p>
</template>
<script>
  name: 'refB',
  props: ['newName'],

  // do not use `()=>{}`
  refName: function () {
    retutn this.newName
  },
  data () {
    return {
      infoB: 'I am ComponentB'
    }
  },
  methods: {
    sayHello () {
      console.log(this.newName)
    }
  }
</script>

License

MIT