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

vue-component-store

v1.0.2

Published

Plugin for keeping the state of your Vue.js application inside components.

Downloads

21

Readme

vue-component-store

License CI npm

A simple plugin for Vue.js 2.5–2.6, offering a clean way to keep the state of your application inside your components.

This library was inspired by https://github.com/LinusBorg/vue-reactive-provide. The basic idea is similar, but the API and implementation are different.

Why?

  1. Vuex is centralized by design, but suggests dividing the store into modules to mimic the application's structure. This usually requires a lot of boilerplate. It's easier to use the existing component hierarchy and Vue's reactivity system directly instead.
  2. Vue has a provide/inject mechanism for passing data down the component hierarchy without chains of props, but it's not reactive by default.

Installation

npm install vue-component-store
import VueComponentStore from 'vue-component-store';

Vue.use(VueComponentStore);

API

You can use the following new options in your components:

  • provideFields – A list of fields (from props, data, or computed) to share with the descendant components. The fields will be reactive (one-way binding, like props).
  • injectFields – A list of fields (provided by ancestor components) to use in the current component. The effect is similar to using mapState and mapGetters from Vuex.
  • provideMethods – A list of methods to share with the descendant components.
  • injectMethods – A list of methods (provided by ancestor components) to use in the current component. This is functionally equivalent to bare inject, but exists for consistency of the API. The effect is similar to using mapActions from Vuex.

In order to share global state between all components in your application, use provideFields/provideMethods in the root component.

Example

See https://github.com/adamsol/vue-component-store/tree/master/test/components/.