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-pursue

v0.1.3

Published

Vue.js or Vuex Plugin to aid Reactivity Tracing / Analysis

Downloads

39

Readme

vue-pursue

Build Status Coverage Status styled with prettier

Vue.js Plugin to examine the dependencies that reactive data has. Intended to be used during development to aid optimization and an understanding of the reactive flow of data.

If reactive data is passed into VuePursue, it will return a list of:

  • computed properties
  • store getters
  • components

These will all refresh if this reactive data is modified.

Why?

Why bother? Well sometimes when writing computed properties or store getters it isn't immediately obvious the impact on performance. In a complex system, long chains of computed/getters can form. Often if data is being denormalized for easy consumption in components or component templates, it can lead to 'overreactivity', where changes to seemly unrelated data can trigger widespread unwanted/unnecessary refreshes.

Installation

npm install vue-pursue

Usage

The library is both a Vue and Vuex plugin, so you can use it in either of the following ways:

Vue.use(VuePursue);

Or as a Vuex store plugin:

new Vuex.Store({ plugins: [VuePursue] });

Note that installing it as a Vuex plugin will automatically install it as a Vue plugin.

Considering the plugin is not intended for production use, but rather as a development aid, a good approach is to include it conditionally:

new Vuex.Store({
  plugins: [
    process.env.NODE_ENV !== 'production' ? VuePursue : () => {}
  ]
});

Debugging

Once the plugin is installed, the pursue function will be available globally via Vue.pursue or VuePursue. The reason it needs to be global is that the best way to use it is within the Developer tools console in your browser.

If I want to find out the impact of changing the value of some reactive data, add a breakpoint just before you plan to change the data (ensuring reactivity has been registered, i.e. all the relevant components depending on this data have been mounted).

Now within the console try any of the following call signatures:

  1. Object - VuePursue(reactiveObject)
  2. Array - VuePursue(reactiveArray)
  3. Object Property - VuePursue(reactiveObject, 'property')
  4. Function - VuePursue(() => reactiveObject.property)

The last option may seem like the best, but be careful with chained access as all levels of reactivity will be examined. (i.e. VuePursue(() => a.b.c) will return reactivity for b and c)

Output

The returned data is an object with the following properties:

  • computed - a list of computed properties ('Component.computedProperty' or 'computedProperty' will be returned depending on whether the component name is available). This list also contains Vuex getters.
  • components - a list of components that will update, i.e. perform a render and use the VDOM to patch the DOM.
  • unrecognised - a count of other watchers that don't fall into the above categories. Should be zero, but if not, a deeper investigation may be needed.

License

MIT