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 🙏

© 2025 – Pkg Stats / Ryan Hefner

vuexer

v0.1.10

Published

Transport data between vue components from npm package and project. Only for Vue 1.

Readme

Vuexer

Vuexer npm version

What's wrong with the "Vue 1 + Vuex 1"?

If you want to distribute some vue 1 components to npm or somewhere else, and these components use Vuex 1 as its state manager, Vue 1 + Vuex 1 just can't do this.

So this package is designed to solve this problem. It adds a new properity $vuexer in all vue components, so that you can use $vuexer as a bridge to communicate with each other.

Only for Vue 1.0, because "Vue 2.0 + Vuex 2.0" has solved this problem.

Quick Start

import Vue from 'vue'
import Vuexer from 'vuexer'

import store from './vuex/store'
import actions from './vuex/actions'
import getters from './vuex/getters'

Vue.use(Vuexer, {
  store,
  actions,
  getters
})

After vuexer has been initialized, a new property called $vuexer will be added to your components.

Let's see:

<script>
  export default {
    methods: {
      setCurrency (num) {
        this.$vuexer.setCurrency(num)  // "setCurrency" is the method that you defined in your vuex actions.
      }
    }
  }
</script>

<template>
  <!-- "getCurrency" is the getter that you have defined in your vuex getters. -->
  <p>currency: {{$vuexer.getCurrency}}</p>
  <div>
    <button @click="setCurrency(10)">I need $10!</button>
    <!-- Or you can also: -->
    <button @click="$vuexer.setCurrency(100)">$100 is required!</button>
  </div>
</template>

Now you want to have this code in your component, and you are going to distribute it to somewhere.

Once a project uses this component, just make sure Vuexer is installed in this project and everything will be fine.

License

Apache-2.0